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: migrate database

Yury Velikanov


Adar absolutely right. Instead to use "cross-platform transportable
tablespace" in case of SYSTEM tablespace you have to use a
"cross-platform transportable DATABASE" feature.
Then you can transport a minimum set of tablespace SYSTEM, UNDO, SYSAUX.
To do that you have to use RMAN, instead of the traditional
transportable tablespace procedure.

If the initial question was: Can I transport a SYSTEM tablespace
across different platforms?
Answer would be: Yes, with some limitations using "cross-platform
transportable DATABASE", and restore through RMAN min set of

Limitation in that case is endian format. It is well described in the
10g doc (see below)

PS Next week I going to play with that feature, moving SYSTEM
tablespace from Linux to Win. Ill update the thread with the results.

Oracle(r) Database
Backup and Recovery Advanced User's Guide
10g Release 2 (10.2)

Page 15-7, Cross-Platform Transportable Database: RMAN CONVERT DATABASE,

Restrictions on Cross-Platform Transportable Database
The principal restriction on cross-platform transportable database is
that the source
and destination platform must share the same endian format. For
example, while you
can transport a database from Microsoft Windows to Linux for x86 (both
or from HP-UX to AIX (both big-endian), you cannot transport a whole
database from
HP_UX to Linux for x86 using this feature. You can, however, create a
new database on
a destination platform manually, and transport needed tablespaces from
the source
database using cross-platform transportable tablespace as described in

On 1/12/06, Yechiel Adar <adar76@(protected):
> The replies I saw are mixing two concepts:
> 1) Using RMAN to copy a DATABASE to new platform, which copy the whole
> database, including system tablespace.
> 2) Using transportable tablespace to move TABLESPACE to a new database
> on another platform.
> I do not know much about RMAN so I will not touch this topic.
> Transportable tablespace is:
> 1) Exporting the metadata that describe the objects in the tablespace.
> 2) Moving the tablespace to the new location.
> 3) Running import tablespace that merge the objects metadata into an
> existing database.
> Since the import works against existing database, and this database
> already have SYSTEM tablespace, you can not do transportable tablespace
> for system.
> Adar Yechiel
> Rechovot, Israel
> Ignizio, Richard wrote:
> >When using Transportable tablespaces you cannot export the SYSTEM tablespace(but you can export the undo tablespace):
> >
> >exec sys.dbms_tts.transport_set_check('SYSTEM');
> >BEGIN sys.dbms_tts.transport_set_check('SYSTEM'); END;
> >
> >
> >
> >
> >
> --
> http://www.freelists.org/webpage/oracle-l

+44 7738 013090 (GMT)