Updating DCNM-LAN Database Name and Username in pgAdmin III
You can update the DCNM-LAN database and username in pgAdmin III.
Step 1 Open the pgAdmin III application.
Step 2 In the Object Browser pane, under Servers, click
PostgreSQL Database Server 8.2
.
In the right-hand pane, the Properties tab appears with several other tabs.
Step 3 On the Properties tab, double-click
Maintenance database
.
A dialog box displays a Properties tab for the server.
Step 4 If you need to change the database name, click the
Maintenance DB
field and type the correct DCNM-LAN database name.
Note The database name should be the name that you specified when you most recently upgraded or reinstalled the DCNM-LAN server software.
Step 5 If you need to change the database username, click the
Username
field and type the correct DCNM-LAN database username.
Note The database username should be the database username that you specified when you most recently upgraded or reinstalled the DCNM-LAN server software.
Step 6 Click
OK
.
Step 7 In the Object Browser pane, double-click
PostgreSQL Database Server 8.2
.
If you changed the username in Step 5, the Connect to Server dialog box appears.
Step 8 If necessary, enter the password for the username that you specified in Step 5 and click
OK
.
The pgAdmin III application connects to the DCNM-LAN database and displays the databases and login roles.
If you need additional assistance, see the Help menu in the pgAdmin III application or see the pgAdmin web site at the following URL:
http://pgadmin.org/docs/1.6/index.html
Trouble with an Oracle Database
If the DCNM-LAN server has trouble using an Oracle database, it logs the error messages in the following file:
Installation_directory
\jboss-4.2.2.GA\server\dcnm\log\server.log
Check
Table 28-3
for symptoms related to using an Oracle database with DCNM-LAN. For each error message, see the possible cause and follow the corresponding solution.
Table 28-3 DCNM-LAN server.log File Errors with an Oracle Database
|
|
|
The following error appears in the server.log file:
java.sql.SQLException: ORA-01653: unable to extend table Cisco DCNMUSER.DCMRAWEVENTTABLE by 1024 in tablespace SYSTEM
|
The tablespace SYSTEM is too small.
|
1. Stop the DCNM-LAN server. See Chapter26, “Starting and Stopping Cisco DCNM-LAN Servers”
2. Increase the SYSTEM table space. For more information, see the
Cisco DCNM Installation and Licensing Guide, Release 7.x
.
3. Start the DCNM-LAN server. See Chapter26, “Starting and Stopping Cisco DCNM-LAN Servers”
|
The following error appears in the server.log file:
[org.hibernate.util.JDBCExceptionReporter] Could not create connection; - nested throwable:
(java.sql.SQLException: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
|
The number of available sessions and processes is inadequate.
|
1. Stop the DCNM-LAN server. See Chapter26, “Starting and Stopping Cisco DCNM-LAN Servers”
2. Increase the number of sessions and processes to 150 each. For more information, see the
Cisco DCNM Installation and Licensing Guide, Release 7.x
.
3. Start the DCNM-LAN server. See Chapter26, “Starting and Stopping Cisco DCNM-LAN Servers”
|
The following error appears in the server.log file:
2009-04-08 15:53:47,125 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
|
The number of open cursors is inadequate.
|
1. Stop the DCNM-LAN server. See Chapter26, “Starting and Stopping Cisco DCNM-LAN Servers”
2. Increase the number of open cursors to 1000. For more information, see the
Cisco DCNM Installation and Licensing Guide, Release 7.x
.
3. Start the DCNM-LAN server. See Chapter26, “Starting and Stopping Cisco DCNM-LAN Servers”
|