Trouble and how to shoot it.

Problem: One of the applications returns an Oracle error message.
Solution: Mostly these indicate a problem with or within the PDB. Some of the numbers indicate that action should be taken, others mean you should jsut try again later.

• ORA-12203 - try again in a few minuites. If the problem persists, email rats_support@email ONCE.  More than likely we already know about it.
• ORA-01843 - you typoed the date.
• SQL-02112 - something is bad with the data. Let us know about it at rats_support@email and please indicate something meaningful about who got the problem. (no SSNs in email please)
• ORA-03113 - try again in a few minuites.
• ORA-00020 - try again in a few minuites. repeat. (the PDB is busy)
• ORA-12537 - try again in a few minuites.

Problem: You just installed RATS and all you get back is garbage.
Solution: Make sure you sent your key pair to rats_support@email, and that you got confirmation that they were added. If you did this, contact rats_support, and verify the keys match what you sent us, and that someone didn't typo something.

Problem: Someone is trying to create an account and they get a not found error.
Solution: This generally means that they are not in the PDB. Use the privileged view to make sure that they are in the PDB, and verify with them that the data they are entering matches what is in the PDB. If they are not in the PDB, send mail to account-support@ns2 with some identifying info. Once again don't email SSNs.

Problem: This person has a weird name, and I'm having trouble finding them even using the privileged view.
Solution: In general, you should try removing any punctuation from the name, and remove any whitespace. Some examples:

•  de Vries -> DEVRIES or DE VRIES
• D'Amico -> DAMICO or D AMICO
• Hennesy-Jones -> HENNESY-JONES, HENNESY JONES, or HENNESYJONES
• Wilks Jr. -> WILKSJR or WILKS JR
• Winston III -> WINSTONIII or WINSTON III

Problem: The wrong name is in the PDB according to privileged view.
Solution: You can tell them to use the wrong spelling to create the account, then point them to the registrar to fix their name if they are a student.

Problem: The wrong IID is in the PDB according to the privileged view.
Solution: If they find this out before an account is created, they should get it fixed before creating an account as it can break things.

Problem: I'm not getting garbage back, but I keep on bombing out when I try to set my UID.
Solution: If you are synchronizing UID space with another cluster, you are probably bombing out because you have not sent them your key and asked for access to the uid calls.

Problem: The user has a username from a pre-rats account, but he can't select it using RATS, and I can't look it up in the PDB through the privileged view.
Solution: This more than likely means either the name has been reserved, or their username was disociated during the move of data from whitepages to the PDB. Contact account_support@ns2.

Problem: The user has an pre-rats account, but cant get into anything like transcripts or schedule of classes.
Solution: If you can check the password file on the authorizing machine, see if the IID in the file matches the IID in priv. view for the person. If not, notify account-support@ns2 and help@<machine> since either side may be in error.