By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,018 Members | 930 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,018 IT Pros & Developers. It's quick & easy.

getting error while calling ADMIN.BACKUPSCHEMA

P: n/a
Hi,

I am getting the error while trying to take a backup of the schema
according to the backupschema.sql written at
http://www-128.ibm.com/developerwork...rticle/dm-0602...

db2 =CALL ADMIN.BACKUPSCHEMA('PKMSQA','/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>

Here PKMSQA is the schema name and '/u01/Backup_schema' is the
directory on AIX.

I am on DB2 9.1 with Aix 5.3.

Can anybody explain why this error is coming?

Please help as this is urgent.

Rahul

P.S. My previous message heading incorrectly stated that i was caaling
ADMIN.COPYSCHEMA, but i was calling ADMIN.BACKUPSCHEMA.
Apologies for the same.

Sep 19 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Rahul Babbar wrote:
Hi,

I am getting the error while trying to take a backup of the schema
according to the backupschema.sql written at
http://www-128.ibm.com/developerwork...rticle/dm-0602...

db2 =CALL ADMIN.BACKUPSCHEMA('PKMSQA','/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>

Here PKMSQA is the schema name and '/u01/Backup_schema' is the
directory on AIX.

I am on DB2 9.1 with Aix 5.3.

Can anybody explain why this error is coming?

Please help as this is urgent.

Rahul

P.S. My previous message heading incorrectly stated that i was caaling
ADMIN.COPYSCHEMA, but i was calling ADMIN.BACKUPSCHEMA.
Apologies for the same.
These are from my developerWorks article?
In 99% of the cases the reason is in permissions.
IMPORT is using the fenced ID (which often is the same as the instance
id). That id needs to have access to the directory.
I do have an improved version of the DDLs. If you ping me I can send it
to you.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Sep 19 '07 #2

P: n/a
On Sep 19, 6:50 pm, Serge Rielau <srie...@ca.ibm.comwrote:
Rahul Babbar wrote:
Hi,
I am getting the error while trying to take a backup of the schema
according to the backupschema.sql written at
http://www-128.ibm.com/developerwork...rticle/dm-0602...
db2 =CALL ADMIN.BACKUPSCHEMA('PKMSQA','/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>
Here PKMSQA is the schema name and '/u01/Backup_schema' is the
directory on AIX.
I am on DB2 9.1 with Aix 5.3.
Can anybody explain why this error is coming?
Please help as this is urgent.
Rahul
P.S. My previous message heading incorrectly stated that i was caaling
ADMIN.COPYSCHEMA, but i was calling ADMIN.BACKUPSCHEMA.
Apologies for the same.

These are from my developerWorks article?
In 99% of the cases the reason is in permissions.
IMPORT is using the fenced ID (which often is the same as the instance
id). That id needs to have access to the directory.
I do have an improved version of the DDLs. If you ping me I can send it
to you.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Serge,

Can you please send the improved version to me. as soon as possible?

Thanks
Rahul

Sep 20 '07 #3

P: n/a
Rahul Babbar wrote:
On Sep 19, 6:50 pm, Serge Rielau <srie...@ca.ibm.comwrote:
>Rahul Babbar wrote:
>>Hi,
I am getting the error while trying to take a backup of the schema
according to the backupschema.sql written at
http://www-128.ibm.com/developerwork...rticle/dm-0602...
db2 =CALL ADMIN.BACKUPSCHEMA('PKMSQA','/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>
Here PKMSQA is the schema name and '/u01/Backup_schema' is the
directory on AIX.
I am on DB2 9.1 with Aix 5.3.
Can anybody explain why this error is coming?
Please help as this is urgent.
Rahul
P.S. My previous message heading incorrectly stated that i was caaling
ADMIN.COPYSCHEMA, but i was calling ADMIN.BACKUPSCHEMA.
Apologies for the same.
These are from my developerWorks article?
In 99% of the cases the reason is in permissions.
IMPORT is using the fenced ID (which often is the same as the instance
id). That id needs to have access to the directory.
I do have an improved version of the DDLs. If you ping me I can send it
to you.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Serge,

Can you please send the improved version to me. as soon as possible?
done

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Sep 20 '07 #4

P: n/a
On Sep 20, 5:08 pm, Serge Rielau <srie...@ca.ibm.comwrote:
Rahul Babbar wrote:
On Sep 19, 6:50 pm, Serge Rielau <srie...@ca.ibm.comwrote:
Rahul Babbar wrote:
Hi,
I am getting the error while trying to take a backup of the schema
according to the backupschema.sql written at
http://www-128.ibm.com/developerwork...rticle/dm-0602...
db2 =CALL ADMIN.BACKUPSCHEMA('PKMSQA','/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>
Here PKMSQA is the schema name and '/u01/Backup_schema' is the
directory on AIX.
I am on DB2 9.1 with Aix 5.3.
Can anybody explain why this error is coming?
Please help as this is urgent.
Rahul
P.S. My previous message heading incorrectly stated that i was caaling
ADMIN.COPYSCHEMA, but i was calling ADMIN.BACKUPSCHEMA.
Apologies for the same.
These are from my developerWorks article?
In 99% of the cases the reason is in permissions.
IMPORT is using the fenced ID (which often is the same as the instance
id). That id needs to have access to the directory.
I do have an improved version of the DDLs. If you ping me I can send it
to you.
Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Serge,
Can you please send the improved version to me. as soon as possible?

done

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Serge,

I am again getting the same error

db2 = call ADMIN.BACKUPSCHEMA('PKMSQA2', '/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>
I have checked that everybody has been given read/write/execute
permissions for the directory (/u01/Backup_schema).
What else could be the error?
Rahul

Sep 21 '07 #5

P: n/a
Rahul Babbar wrote:
On Sep 20, 5:08 pm, Serge Rielau <srie...@ca.ibm.comwrote:
>Rahul Babbar wrote:
>>On Sep 19, 6:50 pm, Serge Rielau <srie...@ca.ibm.comwrote:
Rahul Babbar wrote:
Hi,
I am getting the error while trying to take a backup of the schema
according to the backupschema.sql written at
http://www-128.ibm.com/developerwork...rticle/dm-0602...
db2 =CALL ADMIN.BACKUPSCHEMA('PKMSQA','/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>
Here PKMSQA is the schema name and '/u01/Backup_schema' is the
directory on AIX.
I am on DB2 9.1 with Aix 5.3.
Can anybody explain why this error is coming?
Please help as this is urgent.
Rahul
P.S. My previous message heading incorrectly stated that i was caaling
ADMIN.COPYSCHEMA, but i was calling ADMIN.BACKUPSCHEMA.
Apologies for the same.
These are from my developerWorks article?
In 99% of the cases the reason is in permissions.
IMPORT is using the fenced ID (which often is the same as the instance
id). That id needs to have access to the directory.
I do have an improved version of the DDLs. If you ping me I can send it
to you.
Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Serge,
Can you please send the improved version to me. as soon as possible?
done

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Serge,

I am again getting the same error

db2 = call ADMIN.BACKUPSCHEMA('PKMSQA2', '/u01/Backup_schema')
SQL0438N Application raised error with diagnostic text: "EXPORT
raised
error". SQLSTATE=78000
db2 =>
I have checked that everybody has been given read/write/execute
permissions for the directory (/u01/Backup_schema).
What else could be the error?
As I said: permissions are nearly always the reason.
Start the debugger (e.g. Developer Workbench) and walk through it.
You should be able to see the original error and go from there.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Sep 21 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.