12300-12399: Multiple Mount

This section lists messages generated by Trusted Oracle7.

Cause:	The database link name specified on the ALTER DATABASE statement is not an ROM: link. Specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.

Action:	Retry the ALTER DATABASE statement using a valid ROM: link to the database to be mounted or opened. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted Oracle7 Server Administrator's Guide for more information about creating database links using the ROM: link type.

ORA-12316 syntax error in database link's connect string

Cause:	The connect string in the CREATE DATABASE LINK statement has a syntactical error.

Action:	Drop the database link and recreate it using valid syntax. See Oracle7 Server SQL Reference for more information about the connect string portion of the CREATE DATABASE LINK statement.

ORA-12317 logon to database (link name name) denied

Cause:	Any of the following:

• Either the user name or password was misspelled.

• The user does not exist in the secondary database.

• The user in the secondary database was not granted the CREATE SESSION system privilege.

• The username/password in the database link definition is invalid for any of the above reasons.

• If database verification of login information is active, then the username and password do not match in the primary and secondary databases.

• If operating system verification of login information is active, then the username does not match in the primary and secondary databases.

• Ask the database administrator for the secondary database to create the user.

• Ask the database administrator for the secondary database to grant the CREATE SESSION system privilege to the user.

• Correct the database link definition.

• Check that username and password match in the primary and secondary databases.

• Check that the username matches in the primary and secondary databases.

Note: Always use operating system authentication in Trusted Oracle7 For more information about the advantages of O/S authentication, see the Trusted Oracle7 Server Administrator's Guide.

Cause:	An attempt was made to mount a secondary database already mounted by the instance.

Action:	No additional action is required to mount the database. To establish access, use the ALTER DATABASE command to open the database.

ORA-12319 database (link name name) is already open

Cause:	An attempt was made to open a secondary database that is already open.

Action:	No additional action is required to establish access.

ORA-12321 database (link name name) is not open and AUTO_MOUNTING=FALSE

Cause:	The instance attempted to mount the secondary database, but it is not open and it is not enabled for automatic mounting.

Action:	Manually mount and open the secondary database using the ALTER DATABASE command with the OPEN and MOUNT options. To allow the instance to mount and open secondary databases automatically, set the AUTO_MOUNTING parameter in the initialization parameter file to TRUE.

ORA-12322 unable to mount database (link name name)

Cause:	This message should be accompanied by additional messages that indicate the cause of the problem.

Action:	Follow the steps outlined in the accompanying messages to resolve the problem.

ORA-12323 unable to open database (link name name)

Cause:	This message should be accompanied by additional messages that indicate the cause of the problem.

Action:	Follow the steps outlined in the accompanying messages to resolve the problem.

ORA-12324 cannot use the ROM: link type on a private database link

Cause:	You can only specify the ROM: link type on a public, not on a private, database link.

Action:	If there is an existing public database link to the secondary database, use that link. If not, and public access to the secondary database is desired, create a public database link to the secondary database using the CREATE DATABASE LINK command.

ORA-12326 database name is closing immediately; no operations are permitted

Cause:	The operation attempted was terminated because the database is closing.

Action:	Wait until the database reopens or contact the database administrator.

ORA-12329 database name is closed; no operations are permitted

Cause:	The operation attempted was terminated because the database is closing.

Action:	Wait until the database reopens or contact the database administrator.

ORA-12333 database (link name name) is not mounted

Cause:	An attempt was made to open a database that is not mounted.

Action:	Mount the database with the ALTER DATABASE command, then reattempt to open the database.

ORA-12334 database (link name name) is still open

Cause:	An attempt was made to dismount a database that is still open.

Action:	Close the database with the ALTER DATABASE command, then reattempt to dismount the database.

ORA-12335 database (link name name) is not open

Cause:	An attempt was made to close a database that is not open.

Action:	The database is closed; proceed with dismounting it.

ORA-12341 maximum number of open mounts exceeded

Cause:	The number specified on the OPEN_MOUNTS parameter in the initialization parameter file exceeds 255, which is the maximum allowed.

Action:	Change the value of this initialization parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255.

ORA-12342 open mounts exceeds limit set on the OPEN_MOUNTS parameter

Cause:	The number of currently open mounts exceeds the value specified in the OPEN_MOUNTS initialization parameter.

Action:	Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.

ORA-12345 user name lacks CREATE SESSION privilege in database (link name name)

Cause:	There are two causes of this message:

• Your username in the second database specified was not granted the CREATE SESSION system privilege.

• The username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege.

• In the first case, check that your username in the secondary database was granted the CREATE SESSION system privilege.

• In the second case, check that the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database.

Cause:	An attempt was made to drop a ROM: database link while it was still mounted and/or opened.

Action:	Close and dismount the database. Then retry the drop statement.

ORA-12351 cannot create view using a remote object which has a remote object reference

Cause:	An attempt was made to create a view that references a remote object that, in turn, references an object on another database. Because the view that you tried to create references a remote object, that object cannot reference an object on another database.

Action:	Choose a different object to reference in your view or change the remote object so that it does not reference another database.

ORA-12352 object name is invalid

Cause:	An attempt was made to reference, or compile against, an object in a secondary database. However, the object is invalid because it is in a secondary database. Therefore, the system cannot validate or recompile it.

Action:	Recompile the invalid object in the secondary database.

ORA-12353 secondary stored object cannot reference remote object

Cause:	You tried either to select from a remote view or execute a remote procedure that references an object on another database. Because the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.

Action:	Choose a different object to reference or change the remote view or procedure so that it does not reference another database.

ORA-12354 secondary object being dropped

Cause:	You tried to access an object, for example, a table or view, on a secondary database that was being dropped.

Action:	Repeat the operation. If you receive the message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact customer support.