dev db issues

Links

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

dev db issues

dev db issues

2005-10-14 - By Thomas Fox

Reply: 1 2

Kevin,

Since you are using NOARCHIVELOG mode, you should be safe to reset the logs.
This erases the redo log information, and wouldn't apply to a production
databasein ARCHIVELOG mode if you wanted to retain the redo information.

Simply:

1. shutdown immediate
2. startup mount
3. alter database open resetlogs

--Tom

--- "O'Donnell, Kevin" <Kevin.ODonnell@(protected)> wrote:

> Hello all, I have a dev db that uses iscsi. The box lost power today and
> is now complaining about being out of sync with the redo logs
>
>
>
> ORA-00283 (See ORA-00283.ora-code.com): recovery session canceled due to errors
>
> ORA-00314 (See ORA-00314.ora-code.com): log 2 of thread 1, expected sequence# 9134 doesn't match 9136
>
> ORA-00312 (See ORA-00312.ora-code.com): online log 2 thread 1: '/ora_base/oradata/dirx/redo02a.log'
>
>
>
> SQL> archive log list;
>
> Database log mode No Archive Mode
>
> Automatic archival Disabled
>
> Archive destination
> /ora_base/app/oracle/product/10.1/db/dbs/arch
>
> Oldest online log sequence 9133
>
> Current log sequence 9134
>
>
>
> I have never seen this in a db. Any suggestions? Could it of been from
> the power loss?
>
>
>
> Kevin O'Donnell
>
> Sr. Database Administrator
>
> Neighborcare Technology Center
>
>
>
> Cell: 443-257-3323
>
> Office: 410-534-1959
>
> e-mail: kevin.odonnell@(protected)
>
>
>
>

__ ____ ____ ____ ____ ____ ______
Yahoo! Music Unlimited
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/
--
http://www.freelists.org/webpage/oracle-l