Home
All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

Re: Machine time change and login/startup problem

Hemant K Chitale

2004-06-16

Replies:

In a database application, you wouldn't be changing your system clock
frequently.
Most applications make use of sysdate from the DB server to log
transactions / timestamps etc.

However, Oracle [till at least 9i], doesn't behave in the manner you describe.
During D.R. and Y2K Testing, people have reset system clocks without impacting
the database [of course, transactions that use sysdate get screwed
up]. Time-stamp
based recovery, however, cannot be performed across the actual time when
the system clock was reset backwards.
Are you sure that the errors you encounter in 10g are related to re-setting the
system clock ? What happens if you shutdown Oracle [Database AND Listener]
before you reset the system clock and restart Oracle after having changed
the system time ?

Hemant

At 12:10 AM Tuesday, you wrote:
>Hi,
>
>We are using 10g on windows and whenever I changes system clock to past,
>oracle doesn't startup. And I get errors:
>


Hemant K Chitale
Oracle 9i Database Administrator Certified Professional
http://web.singnet.com.sg/~hkchital

All the suffering in the world arises out of wanting happiness for self.
All happiness in the world arises out of wanting happiness for others.
- Shantideva


Hemant K Chitale
Oracle 9i Database Administrator Certified Professional
http://web.singnet.com.sg/~hkchital


----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------