ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string)

Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege.

Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.

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

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-12341: maximum number of open mounts exceeded

Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).

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

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-12336: cannot login to database (link name string)

Cause: You are tyring to login while another user is mounting or dismounting the same database.

Action: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

Cause: You attempted to close a database that is not open.

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

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

Cause: You attempted to dismount a database that is still open.

Action: Close the database with the ALTER DATABASE CLOSE command, then re-attempt to dismount the database.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

Cause: You attempted to open a database that has not been mounted.

Action: Mount the database with the ALTER DATABASE MOUNT command, then re-attempt to open the database.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-12329: database string is closed; no operations are permitted

Cause: The database you attempted to access is closed, so your operation has been terminated.

Action: Wait until the database is reopened, or contact the database administrator.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

Cause: The database you attempted to access is closing, so your operation has been terminated.

Action: Wait until the database has been reopened, or contact the database adminstrator.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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 a private, database link.

Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/