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

Yury Velikanov

2006-01-20

Replies:
On 1/12/06, Jurijs Velikanovs <j.velikanovs@(protected):
> PS Next week I going to play with that feature, moving SYSTEM
> tablespace from Linux to Win. Ill update the thread with the results.

As promised I have played with "Transportable Databases" feature and
ready to share the results with the list.
Overall impression: The feature is useless. At least in current
version (10G R2).

I have successfully copied 10.2.0.1 db files from Linux to Windows and
opened the database.

However please be aware that directly coping database files is
unsupported way to transfer database from one platform to another. You
have to use RMAN to do that (please see parts of the Oracle doc. and
bug published in Metalink at the end of this post).

There are additional limitations which make the "sexy" feature useless
in real world.
1. You can't use existing backups of source database, you advised to
use the ONLINE source db.
2. Source db (online db) must be opened in "READ ONLY" mode during
RMAN command "CONVERT DATABASE NEW DATABASE" execution.
3. You CAN NOT transform a database between platforms with different
ENDIAN format!

Gant summary: Use "Transportable Tablespace" feature if you need to
move data from platform to platform. If you would like to move a whole
db, then advisable procedure on 10G R2 would be: a) create new db on
target platform (apply all patches you have got on source), use TT
feature to move all your data files, use Full import (or data pump) to
import all PL/SQL objects (data=no).

I hope somebody will hind this information useful.
Jurijs

PS Doc:
-- Metalink Bug No. 4261239 --
At this point the issue is known to be a documentation issue, not a
software issue.
I will close the bug as soon as I have the developer's agreement that
the documentation now correctly reflects the behavior of the feature.

RMAN reference and B&R Advanced Book been updated as of 27 April-- see entry
for CONVERT TABLESPACE and CONVERT DATAFILE in reference, and new chapter on
CONVERT TABLESPACE and CONVERT DATABASE in advanced book...

-- Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) --
Note: In spite of the fact that the endian formats for the source and
destination platform are the same, the datafiles for a transportable
database must undergo a conversion process and cannot simply be
copied directly from one platform to another, as is possible with
transporting tablespaces.
Unlike transporting tablespaces across platforms, transporting entire
databases requires that certain types of blocks, such as blocks in undo
segments, be reformatted to ensure compatibility with the destination
platform.

On 1/12/06, Jurijs Velikanovs <j.velikanovs@(protected):
> 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
> tablespaces.
>
> Limitation in that case is endian format. It is well described in the
> 10g doc (see below)
> Cheers,
> Jurijs
>
> 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)
> B14191-01
>
> 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
> little-endian),
> 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
> >
> >
> >
>
>
> --
> Jurijs
> +44 7738 013090 (GMT)
> ============================================
> http://otn.oracle.com/ocm/jvelikanovs.html
>


--
Jurijs
+44 7738 013090 (GMT)
============================================
http://otn.oracle.com/ocm/jvelikanovs.html
--
http://www.freelists.org/webpage/oracle-l