| Solution ID: prim33933 |
| Receive error running Database Configuration for Project Management: "Unable to connect to database" "Public Login successful, Bad Private username or password." |
| Status: Reviewed |
| Version(s): 4.0, 4.1, 5.0 |
| Fact: | Multiple PMDB Project Management database schemas in one Oracle instance. |
| Fact: | Oracle |
| Problem: | Receive error running Database Configuration for Project Management: “Unable to connect to database” “Public Login successful, Bad Private username or password.” with multiple PMDB Project Management database schemas in one Oracle instance. |
| Problem: | from user (admuser, privuser, pubuser) to user (admuser1, privuser1, pubuser1) |
| Fix: | If the schema users (admuser, privuser, pubuser) are changed from the default during an Oracle import, for example (admuser, privuser, pubuser) are imported into (admuser1, privuser1, pubuser1) , the synonyms created for the new schema users still point to the original tables and must be dropped and recreated for the new schema users. That is, importing from privuser to privuser1, the synonms are created for privuser1 however the synonyms point to the admuser tables. NOTE: Even though the synonyms are not pointing to the desired tables, they do exist so ValSchema will not report these are errors. - Synonyms must be dropped for privuser and pubuser using the ordp_syn.sql provided on CD1:\install\database\scripts\install\or\drop\pmdb MODIFIED FOR YOUR SCHEMA USERS - Then synonyms and grants must be recreated by modifying the SQL statements for creating synonyms and grants in the manual oracle create script on CD1\install\database\scripts\install\or\orpm_ins.sql MODIFIED FOR YOUR SCHEMA USERS example script: new_syngrnt_priv1.sql |