Oracle Switch TP1996-9.2.2.1A Manuel D’Utilisation
Agile 9.2.2.1
y
Verify that the service name exists in one of the tnsnames.ora files. Add the service name,
if necessary.
if necessary.
y
Make sure there are no syntax errors in the tnsnames.ora file, especially unmatched
parentheses or stray characters.
parentheses or stray characters.
Why did I receive an Invalid User Name or Password error in the AUT.log file?
You may receive this error if the database connection was not successful. The following Oracle
error messages may be displayed:
error messages may be displayed:
EXP-00004: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
ORA-01017: invalid username/password; logon denied
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The
username and password must be the same as was specified in a GRANT CONNECT
statement. If the username and password are entered together, the format is
username/password.
username and password must be the same as was specified in a GRANT CONNECT
statement. If the username and password are entered together, the format is
username/password.
Action: Enter a valid username and password combination in the correct format.
What errors would I see if an import fails?
An import can end abnormally due to some of the following reasons:
IMP-00009: abnormal end of export file
Cause: The export file is probably from an aborted Export session.
Action: If so, retry the export and import.
IMP-00013: only a DBA can import a file exported by another DBA
Cause: The privileges needed to import an export file generated by a database administrator do
not exist. Only a database administrator can import such files.
not exist. Only a database administrator can import such files.
Action: The source and destination database users should have the same roles and privileges.
Because the source database has the DBA role, the database destination should also have the
role. If you do not want the destination database to have the DBA role, then remove the role
from the source database and retry the upgrade.
Because the source database has the DBA role, the database destination should also have the
role. If you do not want the destination database to have the DBA role, then remove the role
from the source database and retry the upgrade.
IMP-00041: Warning: object created with compilation warnings
Cause: The object in the SQL statement following this error was created with compilation errors.
If this error occurred for a view, it is possible that the base table of the view was missing or
altered.
If this error occurred for a view, it is possible that the base table of the view was missing or
altered.
Action: This is a warning. The object may have to be recompiled before being used.
Why is AUT hanging?
AUT may not be hanging. Processes may be running that seem to take longer than others. For
example:
example:
y
Indexes may be missing on the source database. If this is the case, averify may be running
slowly.
slowly.
y
The import may be taking a longer time because it’s a large database.
Page - 22
Database Upgrade Guide