What Can I Do When eSight Startup Fails Due to Database Disconnection
Question
If the database is disconnected, eSight startup may fail.
Answer
- Microsoft SQL Server 2012 R2 is used as an example
- Choose Start > All Programs > Microsoft SQL Server 2012 R2 > Configuration Tools > SQL Server Configuration Manager.
The SQL Server Configuration Manager window is displayed.
- Click SQL Server Services. In the right pane, right-click SQL Server (MSSQLSERVER), and choose Start.
- Choose Start > All Programs > Microsoft SQL Server 2012 R2 > Configuration Tools > SQL Server Configuration Manager.
Here, MSSQLSERVER indicates a SQL Server database instance name. It must be replaced by the actual instance name.
For details about eSight full system backup and restoration on the Windows operating system, see Backing Up eSight Full System (Windows) in Maintenance Guide.
- Oracle
- Log in to the SUSE Linux as user oracle.
- On the command line interface (CLI), run the following command to connect to the Oracle database:
$ sqlplus / as sysdba
The user name and password are required in remote login mode. The following describes how to use the command to connect the system user to the Oracle database with password testpwd.
$ sqlplus system/testpwd as sysdba
If the information similar to the following is displayed, the system user is connected to the Oracle database:
SQL >
- Run the following command to start the Oracle database:
Before starting the Oracle database, you can check whether the Oracle database has started.
> select * from v$version;
> startup
If the following information is displayed, the Oracle database is successfully started:
ORACLE instance started.
Total System Global Area 1610612736 bytes
Fixed Size 2046264 bytes
Variable Size 385877704 bytes
Database Buffers 1207959552 bytes
Redo Buffers 14729216 bytes
Database mounted.
Database opened.