PS:
1、ora_startup.bat:
net start OracleOraHome81TNSListener
net start ORACLESERVICEORADB

net stop OracleOraHome81TNSListener
net stop ORACLESERVICEORADB

windows 95/98 client
sql*Net 2.x - ORAWIN95NETWORKADMIN
Net8 - ORAWIN95NET80admin
Net8i - ORACLEORA81NETWORKADMIN
windows NT client
sql*Net 2.x - ORANTNETWORKADMIN
Net8 - ORANTNET80ADMIN
Net8i - ORACLEORA81NETWORKADMIN
UNIX Client
$ORACLE_HOME/NETWORK/ADMIN
or /etc
or /var/opt/oracle

DEV1.WORLD =
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = tcp) (Host = 145.45.78.56) (Port = 1521) ) )
(CONNECT_DATA = (SID = ORCL) ) )

TRACE_LEVEL_CLIENT = OFF
SQLNET.AUTHENTICATION_SERVICES = (NONE)
NAMES.DIRECTORY_PATH = (TNSNAMES)
AUTOMATIC_IPC = OFF

DEV1 =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (Host = 145.45.78.56) (Port = 1521) ) )
(CONNECT_DATA = (SID = ORCL) ) )

Error Id: ORA-12154

Title: TNS:could not resolve the connect identifier specified

Description:

TNS:could not resolve the connect identifier specified

Action:

- If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

Cause:

A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.

Error Id: ORA-01155

Title: the database is being opened, closed, mounted or dismounted

Description:

the database is being opened, closed, mounted or dismounted

Action:

Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work.

Cause:

The requested operation needs the instance to be in a particular state but the state is being changed.

Error Id: ORA-12541

Title: TNS:no listener

Description:

TNS:no listener

Action:

Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.

Cause:

The connection request could not be completed because the listener is not running.

Error Id: ORA-12500

Title: TNS:listener failed to start a dedicated server process

Description:

TNS:listener failed to start a dedicated server process

Action:

Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support.

Cause:

The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly.

Error Id: ORA-00405

Title: compatibility type "string"

Description:

compatibility type "string"

Action:

See accompanying error

Cause:

Reporting a type associated with another error.

Error Id: ORA-12560

Title: TNS:protocol adapter error

Description:

TNS:protocol adapter error

Action:

Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.

Cause:

A generic protocol adapter error occurred.

Error Id: TNS-12560

Title: TNS:protocol adapter error

Description:

TNS:protocol adapter error

Action:

Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.

Cause:

A generic protocol adapter error occurred.

Error Id: TNS-12537

Title: TNS:connection closed

Description:

TNS:connection closed

Action:

None needed; this is an information message.

Cause:

"End of file" condition has been reached; partner has disconnected.

Error Id: TNS-12533

Title: TNS:illegal ADDRESS parameters

Description:

TNS:illegal ADDRESS parameters

Action:

Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.

Cause:

An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport.

Error Id: TNS-00507

Title: Connection closed

Description:

Connection closed

Action:

None needed; this is an information message.

Cause:

Normal "end of file" condition has been reached; partner has disconnected.

Error Id: TNS-01155

Title: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA

Description:

Incorrectly specified SID_LIST_string parameter in LISTENER.ORA

Action:

Be sure this parameter is specified as described in the Oracle9i Net Services Reference Guide. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))

Cause:

SID_LIST_<listener_name> in LISTENER.ORA has an error in it.

Error Id: TNS-12203

Title: TNS:unable to connect to destination

Description:

TNS:unable to connect to destination

Action:

Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node.

Cause:

Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems.

Error Id: TNS-12154

Title: TNS:could not resolve the connect identifier specified

Description:

TNS:could not resolve the connect identifier specified

Action:

- If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

Cause:

A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.

-- 来自：