export

[tharakab]

Dear Friends,
Pl. look into the following problem:

1) I have various databases on a Unix Box
2) By default the oracle_SId will be set to a database by name GTRN. Hence when I log on to Unix box my oracle_sid will be GTRN
3) I have another database UTL1
4) I have issued the following command to export a user's table, but i get the below mentioned error:
au19ora:GTRN> echo $ORACLE_SID
GTRN
au19ora:GTRN> exp bt/bt@utl1 tables=bt

Export: Release 7.3.3.5.0 - Production on Fri Nov 29 16:53:17 2002

Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.


EXP-00008: ORACLE error 942 encountered
ORA-00942: table or view does not exist
EXP-00222:
System error message 2
EXP-00024: Export views not installed, please notify your DBA
EXP-00000: Export terminated unsuccessfully

5) But, when I change the environment using . oraenv and set to UTL1, the export runs through successfully. Can someone explain why I am getting an error in step 4 though I am using the Connect string

[pravin]

ORACLE_HOME=/U01/app/oracle/product/8.1.7;export ORACLE_HOME
ORACLE_SID=ABC;export ORACLE_SID

try giving the full path name so that it can identify.
c:\oracle\ora81\bin exp bt/bt@utl1 tables=bt

[sai_sathish]

It is better practice to export the Oracle environment variables before you connect to the database.

[tharakab]

Praveen,

Since there are 2 oracle_homes on the box and GTRN being 7.3 and UTL! being 8.0.5.2.2 I changed my path to 8.0.5.2.2 Home directory's bin and ran the export again without chaging ORACLE_SID,since I am giving the hoststring. But I am getting the
following error:
au19ora:GTRN> exp bt/bt@utl1 tables=bt

Export: Release 8.0.5.2.2 - Production on Fri Nov 29 18:5:13 2002

(c) Copyright 1998 Oracle Corporation. All rights reserved.


Connected to: Oracle8 Enterprise Edition Release 8.0.5.2.2 - Production
With the Partitioning and Objects options
PL/SQL Release 8.0.5.2.1 - Production
Export done in US7ASCII character set

About to export specified tables via Conventional Path ...Memory fault(coredump)

[eeswar]

Please check the free space available in the filesystem. This could be due to space problem.

[tharakab]

eshwar,

There is ample space on the filesystem. As sai has mentioned it is always a good practice to export environment variables though we are using the connect string.

Thank you all for your answers

[pravin]

memory fault coredump comes when there is space constraint in the files system. check if there is space in the o/s file system

[tharakab]

pravin,

there is sufficient space on the filesystem

[prakashs43]

did u check the owner of the filesystem .
which version are u using it could be a bug .

[tycho]

Hi,

This is the problem:
GTRN being 7.3
UTL1 being 8.0.5.2.2

The exp utility is version specific. Version 7.3 uses different views compared to version 8.0.5 so you cann't use exp 8.0.5 against a 7.3 database.

If you change your env to a different 7.3 you can exp against the GTRN database.

tycho