Hello,
We are encountering ASE error 14545 when completing the following steps:
1. Create a dump from a source database (let's say in this instance of ASE, dbid=37).
2. We list this database dump with HEADERONLY to parse out some details:
3216:Backup Server session id is: 341. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
3136:Database log version=7; database upgrade version=35; database durability=UNDEFINED.
3025:Dump is password-protected, a valid password is required.
3124:This is a database dump of database ID 37, name 'GRDS_REP_DB02', from Jun 24 2016 10:30AM. ASE version: Adaptive Server Enterprise/15.7.0/EBF 22310 SMP SP61 /P/x86_64/Enterprise Linux/ase157sp6x/3341/64-b. Backup Server version: Backup Server/15.7/EBF 22310 SP61/P/Linux AMD Opteron/Enterprise Linux/ase157sp6x/4177/64-bit/OPT/F. Database page size is 2048.
2. In a second instance of ASE we create a staging database to load the dump from the original database into using the "WITH DBID" clause (dbid=10241). We do this in an attempt:
CREATE DATABASE dxnev88xv0our715c9_neal ON dx9vzdP3zU95v7f9PoPJ35_0_dat='2048K',dx5aN3kHLHwhPv3tvgpvXb_1_dat='2048K',dxm79D779e8A2vtfR4uVfN_2_dat='2048K',dxh6OtbvSk9fwv9vuh875v_3_dat='2048K',dxPXr3xu3gvX52flH8A17z_4_dat='2048K',dxvz9389ub6E93L7P1QI3v_5_dat='2048K',dxy4ZnP4Q7pfu399e3w778_6_dat='2048K',dxr2nl5zPP8g933fsfxI19_7_dat='2048K' WITH dbid=10241 FOR LOAD
3. Then we load the dump from the first instance of ASE into the staging database on the second instance of ASE:
LOAD DATABASE dxnev88xv0our715c9_neal FROM '/export/home/sybase/dump/neal.full.6'
4. Then we temporarily unmount the database to create a manifest file:
UNMOUNT DATABASE [dxnev88xv0our715c9_neal] to '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/manifest' WITH OVERRIDE
5. Then we do a "MOUNT with LISTONLY" to build up a list of devices:
MOUNT DATABASE all FROM '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/manifest' WITH LISTONLY
6. Finally when we try to mount the staging database but this fails with ASE error 14545:
MOUNT DATABASE [dxnev88xv0our715c9_neal] AS [dxnev88xv0our715c9_neal] FROM '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/manifest' USING '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dxm79D779e8A2vtfR4uVfN_2.dat' = 'dxm79D779e8A2vtfR4uVfN_2_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dxr2nl5zPP8g933fsfxI19_7.dat' = 'dxr2nl5zPP8g933fsfxI19_7_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dx9vzdP3zU95v7f9PoPJ35_0.dat' = 'dx9vzdP3zU95v7f9PoPJ35_0_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dxh6OtbvSk9fwv9vuh875v_3.dat' = 'dxh6OtbvSk9fwv9vuh875v_3_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dx5aN3kHLHwhPv3tvgpvXb_1.dat' = 'dx5aN3kHLHwhPv3tvgpvXb_1_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dxvz9389ub6E93L7P1QI3v_5.dat' = 'dxvz9389ub6E93L7P1QI3v_5_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dxy4ZnP4Q7pfu399e3w778_6.dat' = 'dxy4ZnP4Q7pfu399e3w778_6_dat', '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-13/datafile/dxPXr3xu3gvX52flH8A17z_4.dat' = 'dxPXr3xu3gvX52flH8A17z_4_dat'
[2016-06-24 18:46:25,984][INFO][ase.dbc.ASEJDBCAccessorImpl#messageHandler:774][Worker-4178|JOB-1473|DB_SYNC(ASE_DB_CONTAINER-348)] ASE message 14545 : Cannot locate the logical page 569856 for database 'dxnev88xv0our715c9_neal', dbid=10241, on the device 'dx5aN3kHLHwhPv3tvgpvXb_1_dat''. The page on the device is logical page 569856 for dbid 37.
In this sequence of events, we never see the warning about "DBCC CHECKALLOC". We never online the database during this process (if that is relevant).
- Are we missing any steps that would help us avoid ASE error 14545?
- Could we run something on the source ASE prior to taking the original dump that would help us avoid the error?
- Should the dbid have been updated during the LOAD DATABASE command?
- Is there anyway around this issue other than upgrading to a version of ASE with CR 798271 fixed?