Hello! We had some problems updating an instance on wednesday from SAP DB 7.3.0.18 to 7.3.0.23.
We're running a test and a productive environment on two different server under SuSE Linux SLES 7 with a 2.4.16-Kernel (exactly: 2.4.16-4GB-SMP built by SuSE). Before updating the prod-system we updated our test-system successfully. Each environment is running approximately 5 instances (I know, we shouldn't). Now let's go to the error(s). I'll describe what we've done: After shutting down all instances and stopping the vserver (x_server) we installed the new RPMs (sapdb-ind-7.3.0.23-1.i386.rpm and sapdb-srv-7.3.0.23-1.i386.rpm): rpm -Uhv sapdb-ind-7.3.0.23-1.i386.rpm sapdb-srv-7.3.0.23-1.i386.rpm This worked very well and a new vserver was running. Then we started the first instance. After it has been in state WARM, we reloaded the system-tables: load_systab -ud <DOMAIN-USER-PASSWORD> As we tried to start the second instance (which is quite huge, around 14 GB) it reached only state COLD and the error-message with code -9400 (no message available) was displayed. We've put the instance to state offline, made a db_clear and db_restart, but the instance went only to state COLD with the -9400 error. The log-files aren't very fruitful. Only the error-message (without description) can be found there. After that we tried to recover the DB but this ended in error -9400 (I'm sorry, that I can't reconstruct the exact commands we have done, because it was rather late [11 pm or so] and we were a bit tired ;-) ). The disks are all OK (we've executed a fs-check). After that we deleted the whole instance and installed a new one (for recovery). After loading all needed Backups (Full, incremental and log) the instance didn't went to state WARM and stopped in state COLD with error -9030. The last action we've done yesterday was to delete the instance and create a new instance (for installation) with the needed space (12 * 1,5 GB for data and 1 * 1,5 GB for log). But this ended in error -9400 too. After that we tried to install an instance with only on data-devspace defined. This worked and after that we added the needed devspaces step by step. This works and we're running now the database and need to fill in the data. Now we're trying to reconstruct this problem on another machine. Do you have any idea for solving this problem? We have backuped some log-files and I hope that we can reconstruct this failure on our second test-system. Please tell me what informations I should send to you and how to retrieve them. Thanks a lot! Greets Christian Jung _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
