now I have another problem:
USE USER DBA DBA;
CATALOGLOAD ALL INFILE '/tmp/cat.dmp'
What exactly is a sysdba?
/ E -25331: This is a restricted statement, user must be SYSDBA.
I created my DBA as in the create_demodb script:
util_connect DBM,pwd
util_execute init config
util_activate DBA,DBA
?
What about the user "SYS"?
Greetings, Andre'
Andre Reitz wrote:> I did two exports:
> via:
> - CATALOGEXTRACT ALL OUTFILE '/tmp/cat.dmp'
> - TABLEEXTRACT ALL OUTFILE '/tmp/tab.dmp'
> the export seems to be done correctly
> when i try to import into a newly created instance
> via:
> - CATALOGLOAD ALL INFILE '/tmp/cat.dmp'
> - TABLELOAD ALL INFILE '/tmp/tab.dmp' OUTFILE '/tmp/restart.dmp'> i get a python-exception:
> repman.CommunicationError: repman.CommunicationError: [1] protocol error> server2 is a linux-rpm-installation of:
> sapdb-ind-7.3.0.20-1
> sapdb-srv-7.3.0.20-1> server1 is a linux-rpm-installation of:
> sapdb-ind-7.3.0.8-1
> sapdb-srv-7.3.0.8-1> I used the ReplicationServer of server2 (7.3.0.20) to
> - export the data from server1 (7.3.0.8)
> - import.the data to server2 (7.3.0.20)may be the bug is fixed by the following patch/update puplished at 01/25/02:
Linux:
ftp://ftp.sap.com/pub/sapdb/bin/patch/sapdb-lserversrv-linux-32bit-i386-7.3.
1.1.tgz
and
Win32:
ftp://ftp.sap.com/pub/sapdb/bin/patch/sapdb-lserver-win32-7.3.1.1.zipThis lserver is of version 7.3.1.1 that is
compatible with 7.3.0.18.For bug fixes and features see the README file included in
the archives.excerpt:
Bug fixes
- Fixed bugs in TABLELOAD command processing:1. The error happened when source and target machine had different swap
behavior.
Loading data using TABLELOAD then stopped with the following error
message:
"/ E -25801: Internal error [<file name>, <line number>, -9053]; contact
technical support".
2. TABLELOAD cmd causes lserver to crash (happened only on linux so far)
If the table to load had indexes defined the TABLELOAD command cores
with the
following messages:
Replication server error (-4 : 'received a garbled packet')
Some error(s) occurred running command.let me know if this patch solves your problem.
--
Hans-Georg Bumes
SAP DB, SAP Labs Berlin
http://www.sapdb.org/
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
-- _____________________________________________ inworks GmbH Andre Reitz Magirusstrasse 44 Tel. 0731/93 80 7-21 89077 Ulm http://www.inworks.de
