Difference between revisions of "XBio:D Database Server Management"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
− | ''' | + | '''xBio:D Database Server Management''' |
+ | |||
+ | |||
+ | == Startup Database == | ||
This section is present to provide a step-by-step manner to restarting the OSUC database. Although the database and all of the web services should automatically begin on startup, these instructions will be valuable if an error does occur. The assumption is that the user is already logged into the OSUC server. | This section is present to provide a step-by-step manner to restarting the OSUC database. Although the database and all of the web services should automatically begin on startup, these instructions will be valuable if an error does occur. The assumption is that the user is already logged into the OSUC server. |
Revision as of 17:48, 21 July 2015
xBio:D Database Server Management
Startup Database
This section is present to provide a step-by-step manner to restarting the OSUC database. Although the database and all of the web services should automatically begin on startup, these instructions will be valuable if an error does occur. The assumption is that the user is already logged into the OSUC server.
- Startup the database: $ dbstart $ORACLE_HOME
- Start the database listener: $ lsnrctl start
////// Everything below is currently deprecated. Custom python middleware is acting as DB gateway //////
- Start up Oracle WebLogic Server: $ $WL_HOME/server/bin/startNodeManager.sh
- Start up Oracle Enterprise Manager Cloud Control (may be deprecated?): $ $AGENT_INSTANCE_HOME/bin/emctl start agent
- Start up Oracle middleware applications: $ $ORACLE_INSTANCE/bin/opmnctl startall
Using Enterprise Manager Cloud Control
- URL: https://osuc.biosci.ohio-state.edu:7802/em
- Username: sysman
- Password: a special derivative