Reddy,

Also you can run the sp_downgrade to your higher version to the desired version and perform the dump and load it to the target machine, also later you can upgrade back to the desired version

PS: I am not sure this will work out or not as I seriously didn't try this option

Also I assume you are not trying this on to your production machine, else I need to give you caution as "I am not responsible for the loss or downtime or any other things on your machine"

Regards

Kiran K Adharapuram

Reddy,

Refer the below infocenter link for the dump and load onto higher version machine:

SyBooks Online

Hello Ganimede,

If possible attach the SID logs, let see if the log file gives some hints on this issue.

Regards

Kiran K Adharapuram

Hi,

as example, jobs end yesterday in the afternoon after 05:15 PM

So in the log there isn't any error message:

Hi,

sometime, on our test system database dump ends with an error message:

starting job execution at 2015-03-10 02:00:01

(1 row affected)

dump database NVQ using config = DBTSMNVQBackup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

(1 row affected)

Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Backup Server session id is: 29. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.

Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.DB.20150310.020002.000::000'Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506901C22 ' section number 1 mounted on byte stream 'syb_tsm::NVQ.DB.20150310.020002.000::000'Backup Ser

VQ: 53440 kilobytes (1%) DUMPED.

Error encountered by Backup Server. Please refer to Backup Server messages for details.

Backup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Backup Server session id is: 32. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.

Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.DB.20150310.020006.000::000'Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506901C26 ' section number 1 mounted on byte stream 'syb_tsm::NVQ.DB.20150310.020006.000::000'

Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020006.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157

Error encountered by Backup Server. Please refer to Backup Server messages for details.

Backup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Backup Server session id is: 35. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.

Backup Server: 4.132.1.1: Attempting to open

byte stream device: 'syb_tsm::NVQ.DB.20150310.020007.000::000'Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506901C27 ' section number 1 mounted on byte stream 'syb_tsm::NVQ.DB.20150310.020007.000::000'Backup Server: 4.124.2.1: Archive API error for device=

Error encountered by Backup Server. Please refer to Backup Server messages for details.

ERROR: Error encountered by %S_MSG. Please refer to %S_MSG messages for details.

In Backup Server Log:

Mar 10 01:22:02 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.012200.000.0,  Copyids: (0, 408302).

Mar 10 01:22:02 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 02:00:02 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:00:02 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:00:02 2015: Backup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

Mar 10 02:00:02 2015: Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Mar 10 02:00:02 2015: Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Mar 10 02:00:02 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 1048576 bytes.

Mar 10 02:00:02 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.DB.20150310.020002.000::000'

Mar 10 02:00:02 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 02:00:03 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506901C22    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.DB.20150310.020002.000::000'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_1\NVQ_data_001.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_2\NVQ_data_002.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_3\NVQ_data_003.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_4\NVQ_data_004.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_5\NVQ_data_005.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_6\NVQ_data_006.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_7\NVQ_data_007.dat'

Mar 10 02:00:03 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_8\NVQ_data_008.dat'

Mar 10 02:00:04 2015: Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020002.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157)  The transaction will be aborted.

Mar 10 02:00:04 2015: Backup Server: 4.188.1.1: Database NVQ: 53440 kilobytes (1%) DUMPED.

Mar 10 02:00:05 2015: Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020002.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157)  The transaction will be aborted.

Mar 10 02:00:05 2015: A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 16, error code=232, system message=Cannot get operating system error tex.

Mar 10 02:00:05 2015: D00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=109, system message=Cannot get operating system error tex.

Mar 10 02:00:06 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:00:06 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:00:06 2015: Backup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

Mar 10 02:00:06 2015: Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Mar 10 02:00:06 2015: Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Mar 10 02:00:06 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 1048576 bytes.

Mar 10 02:00:06 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.DB.20150310.020006.000::000'

Mar 10 02:00:06 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 02:00:06 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506901C26    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.DB.20150310.020006.000::000'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_1\NVQ_data_001.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_2\NVQ_data_002.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_3\NVQ_data_003.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_4\NVQ_data_004.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_5\NVQ_data_005.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_6\NVQ_data_006.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_7\NVQ_data_007.dat'

Mar 10 02:00:06 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_8\NVQ_data_008.dat'

Mar 10 02:00:07 2015: Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020006.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157)  The transaction will be aborted.

Mar 10 02:00:07 2015: Backup Server: 4.188.1.1: Database NVQ: 10536 kilobytes (1%) DUMPED.

Mar 10 02:00:07 2015: A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 16, error code=232, system message=Cannot get operating system error tex.

Mar 10 02:00:07 2015: D00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=109, system message=Cannot get operating system error tex.

Mar 10 02:00:07 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:00:07 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:00:07 2015: Backup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

Mar 10 02:00:07 2015: Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Mar 10 02:00:07 2015: Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Mar 10 02:00:07 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 1048576 bytes.

Mar 10 02:00:07 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.DB.20150310.020007.000::000'

Mar 10 02:00:07 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 02:00:08 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506901C27    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.DB.20150310.020007.000::000'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_1\NVQ_data_001.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_2\NVQ_data_002.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_3\NVQ_data_003.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_4\NVQ_data_004.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_5\NVQ_data_005.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_6\NVQ_data_006.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_7\NVQ_data_007.dat'

Mar 10 02:00:08 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sapdata_8\NVQ_data_008.dat'

Mar 10 02:00:09 2015: Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020007.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157)  The transaction will be aborted.

Mar 10 02:00:09 2015: Backup Server: 4.188.1.1: Database NVQ: 21290 kilobytes (1%) DUMPED.

Mar 10 02:00:10 2015: Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020007.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157)  The transaction will be aborted.

Mar 10 02:00:10 2015: A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 16, error code=232, system message=Cannot get operating system error tex.

Mar 10 02:00:10 2015: D00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=109, system message=Cannot get operating system error tex.

Mar 10 02:22:01 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 02:22:02 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 02:22:02 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.TRAN.20150310.022201.000::000'

Mar 10 02:22:02 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 02:22:02 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506902149    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.TRAN.20150310.022201.000::000'

Mar 10 02:22:02 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 02:22:06 2015: Backup Server: 4.58.1.1: Database NVQ: 75286 kilobytes DUMPED.

Mar 10 02:22:06 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 02:22:06 2015: Backup Server: 4.58.1.1: Database NVQ: 75308 kilobytes DUMPED.

Mar 10 02:22:06 2015: Backup Server: 4.190.1.1: Database NVQ: Verification reported 0 errors.

Mar 10 02:22:06 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.022201.000.0,  Copyids: (0, 408309).

Mar 10 02:22:06 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 03:22:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 03:22:01 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 03:22:01 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.TRAN.20150310.032200.000::000'

Mar 10 03:22:01 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 03:22:01 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506902F58    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.TRAN.20150310.032200.000::000'

Mar 10 03:22:01 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 03:22:01 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 03:22:01 2015: Backup Server: 4.58.1.1: Database NVQ: 1132 kilobytes DUMPED.

Mar 10 03:22:01 2015: Backup Server: 4.190.1.1: Database NVQ: Verification reported 0 errors.

Mar 10 03:22:02 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.032200.000.0,  Copyids: (0, 408313).

Mar 10 03:22:02 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 04:22:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 04:22:01 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 04:22:01 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.TRAN.20150310.042200.000::000'

Mar 10 04:22:01 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 04:22:01 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506903D68    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.TRAN.20150310.042200.000::000'

Mar 10 04:22:01 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 04:22:02 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 04:22:02 2015: Backup Server: 4.58.1.1: Database NVQ: 1180 kilobytes DUMPED.

Mar 10 04:22:02 2015: Backup Server: 4.190.1.1: Database NVQ: Verification reported 0 errors.

Mar 10 04:22:02 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.042200.000.0,  Copyids: (0, 408317).

Mar 10 04:22:02 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 05:22:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 05:22:01 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 05:22:01 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.TRAN.20150310.052200.000::000'

Mar 10 05:22:01 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 05:22:02 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506904B78    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.TRAN.20150310.052200.000::000'

Mar 10 05:22:02 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 05:22:02 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 05:22:02 2015: Backup Server: 4.58.1.1: Database NVQ: 1116 kilobytes DUMPED.

Mar 10 05:22:02 2015: Backup Server: 4.190.1.1: Database NVQ: Verification reported 0 errors.

Mar 10 05:22:03 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.052200.000.0,  Copyids: (0, 408321).

Mar 10 05:22:03 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 06:22:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 06:22:01 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 06:22:01 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.TRAN.20150310.062200.000::000'

Mar 10 06:22:01 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 06:22:02 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506905988    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.TRAN.20150310.062200.000::000'

Mar 10 06:22:02 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 06:22:02 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 06:22:02 2015: Backup Server: 4.58.1.1: Database NVQ: 1148 kilobytes DUMPED.

Mar 10 06:22:02 2015: Backup Server: 4.190.1.1: Database NVQ: Verification reported 0 errors.

Mar 10 06:22:02 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.062200.000.0,  Copyids: (0, 408325).

Mar 10 06:22:03 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 07:22:01 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 07:22:02 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 07:22:02 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::NVQ.TRAN.20150310.072201.000::000'

Mar 10 07:22:02 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 07:22:02 2015: Backup Server: 6.28.1.1: Dumpfile name 'NVQ1506906799    ' section number 1 mounted on byte stream 'syb_tsm::NVQ.TRAN.20150310.072201.000::000'

Mar 10 07:22:02 2015: D00: Attempting non buffered I/O for device 'T:\sybase\NVQ\saplog_1\NVQ_log_001.dat'

Mar 10 07:22:02 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 07:22:02 2015: Backup Server: 4.58.1.1: Database NVQ: 1116 kilobytes DUMPED.

Mar 10 07:22:02 2015: Backup Server: 4.190.1.1: Database NVQ: Verification reported 0 errors.

Mar 10 07:22:03 2015: A00: Database 'NVQ' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /NVQ.XACT, low = /NVQ.TRAN.20150310.072201.000.0,  Copyids: (0, 408329).

Mar 10 07:22:03 2015: Backup Server: 3.42.1.1: DUMP is complete (database NVQ).

Mar 10 08:00:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 08:00:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 08:00:00 2015: Backup Server: 4.171.1.1: The current value of 'reserved pages threshold' is 85%.

Mar 10 08:00:00 2015: Backup Server: 4.171.1.2: The current value of 'allocated pages threshold' is 40%.

Mar 10 08:00:00 2015: Backup Server: 4.171.1.5: The current value of 'parallel scan' is 2.

Mar 10 08:00:00 2015: Backup Server: 1.70.1.2: Configuring the shared memory per stripe to 786432 bytes.

Mar 10 08:00:00 2015: Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::master.DB.20150310.080000.000::000'

Mar 10 08:00:00 2015: A00: Tivoli Storage Manager API: version = 7, release = 1, level = 1.

Mar 10 08:00:01 2015: Backup Server: 6.28.1.1: Dumpfile name 'master1506907080 ' section number 1 mounted on byte stream 'syb_tsm::master.DB.20150310.080000.000::000'

Mar 10 08:00:01 2015: D00: Attempting non buffered I/O for device 'P:\sybase\NVQ\sybsystem\master.dat'

Mar 10 08:00:01 2015: Backup Server: 4.188.1.1: Database master: 3540 kilobytes (5%) DUMPED.

Mar 10 08:00:01 2015: Backup Server: 4.188.1.1: Database master: 12230 kilobytes (11%) DUMPED.

Mar 10 08:00:01 2015: Backup Server: 4.188.1.1: Database master: 15960 kilobytes (100%) DUMPED.

Mar 10 08:00:02 2015: Backup Server: 3.43.1.1: Dump phase number 1 completed.

Mar 10 08:00:02 2015: Backup Server: 3.43.1.1: Dump phase number 2 completed.

Mar 10 08:00:02 2015: Backup Server: 3.43.1.1: Dump phase number 3 completed.

Mar 10 08:00:02 2015: Backup Server: 4.188.1.1: Database master: 15982 kilobytes (100%) DUMPED.

Mar 10 08:00:02 2015: Backup Server: 4.190.1.1: Database master: Verification reported 0 errors.

Mar 10 08:00:02 2015: A00: Database 'master' dumped. Tivoli Storage Manager backup object name: fs = /NVQ, high = /master.DB, low = /master.DB.20150310.080000.000.0,  Copyids: (0, 408331).

Mar 10 08:00:02 2015: Backup Server: 3.42.1.1: DUMP is complete (database master).

Mar 10 08:10:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Mar 10 08:10:00 2015: Backup Server: 2.23.1.1: Connection from Server NVQ on Host  with HostProcid 6032.

Have you got any idea?

Thank you.

I am trying to load from higher version to smaller one i seen i remember from lower to higher we do it that way

Just want to know from anyone if the upgrade is the only way to get the data dump and load or anytother procedure....

Hi,

Just for the record: this disucssion should be moved to the ASE for custom applications comunity http://scn.sap.com/community/ase-custom-applications

Regards,
Victoria.

Hello Victoria,

As You Say Victoria
We will discuss in that Community

Regards

Kiran K Adharapuram

There is an open CR to have the backupserver errorlog suggest checking the Tivoli server log when this error is reported:

Mar 10 02:00:07 2015: Backup Server: 4.124.2.1: Archive API error for device='syb_tsm::NVQ.DB.20150310.020006.000::000': Vendor application name=Sybase-TSM API, Library version=2, API routine=syb_write(), Message=Tivoli Storage Manager error returned. Message = ANS0278S (RC157)  The transaction will be aborted.

The reason is that this error may be reported when the TSM server activity log says that TSM Server is not in compliance with License terms. This is because IBM provides 1 month Evaluation License for Tivoli Storage Manager and Archive Manager when a new TSM server is initialized. The TSM server may have to be reinitied to proceed with dump/load activity as solution to this issue.

To see if that is indeed the cause for your problem, check the Tivoli log for messages like these:

File 'initserv.log':

ANR2803I License manager started.

ANR9632I Cannot load licensing DLL library: ADSMLICN.DLL : the server will

assume evaluation licensing mode.

ANR9651I An EVALUATION LICENSE for IBM System Storage Archive Manager will

expire on 04/15/2010.

ANR9651I An EVALUATION LICENSE for Tivoli Storage Manager Basic Edition will

expire on 04/15/2010.

ANR9651I An EVALUATION LICENSE for Tivoli Storage Manager Extended Edition

will expire on 04/15/2010.

Hello,

We are observing that Sybase db is causing high CPU usages on the server.

What I need to do in this case?

Environment: Adaptive Server Enterprise/15.7/EBF 21152 SMP SP100 on Linux.

Appreciate any feedback.

Thanks

Sagar

Hello Ganimede,

As per the error log, you got 605 error:

An attempt was made to fetch logical page '15943' from cache 'default data cache'. Page belongs to database 'saptools' (5), object 'DBH_STG_SPINLOCKACTVTY' (1452529177), index 'DBH_STG_SPINLOCKACTVTY' (0), partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (1452529177) and not to database 'saptools' (5), object 'DBH_SNAP_CACHEDOBJECTS' (249048892), index 'DBH_SNAP_CACHEDOBJECTS' (0), partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (249048892).

followed by reorg for the same table:

SQL causing error : REORG DEFRAG DBH_SNAP_CACHEDOBJECTS WITH SKIP_COMPACT_EXTENTS = 90

1. Run the dbcc checktable command on the second object specified

in the error message.

2. To help determine the full extent of the corruption, run the dbcc

checkdb and dbcc checkalloc commands as soon as feasible.

3. Check the Adaptive Server error log for other errors which often

accompany a 605 error. If the 605 error is not transient, the

problem is severe and you will probably need to restore from

known clean backups.

Regards

Kiran K Adharapuram

Hi guys

This error is kinda odd since i have installed 3 systems under the same OS/DB Conditions

Windows 2012 R2 with ASE 15.7.

14GB Memory

30GB PageFile

Firewall Off

On the previous two systems, when executing a System Copy using an Export File it completed with no problems.

On this System Installation, during ASE Server Setup, SAPINST fails, checking ASE logs it seems releted to memory, but I cant figure out what is the problem since 14GB would be enough, and it never happened on the previous installations.

Any idea what could be causing this?

init logs.

Finished loading file 'charset.loc'.
03/13/15 06:23:20 AM End output from 'charset'.
03/13/15 06:23:20 AM Character set 'utf8' has been successfully installed.
03/13/15 06:23:20 AM Task succeeded: install a character set(s).
03/13/15 06:23:20 AM Running task: set the default character set and/or default
                     sort order for the Adaptive Server.
03/13/15 06:23:20 AM Setting the default character set to utf8
03/13/15 06:23:20 AM Sort order 'binary' has already been installed.
03/13/15 06:23:21 AM SQL command: exec sp_configure 'default character set id',
                     190, binary
03/13/15 06:23:21 AM SQL command: exec sp_configure 'default sortorder id', 25,
                     utf8
03/13/15 06:23:21 AM Sort order 'binary' has been successfully set to the
                     default.
03/13/15 06:23:23 AM SQL command: shutdown
03/13/15 06:23:25 AM Waiting 15 seconds for the operating system to reclaim
                     resources before rebooting.
03/13/15 06:23:45 AM Calling the shell with
                     '"J:\sybase\AEC\ASE-15_0\bin\sqlsrvr.exe"
                     -d"J:\sybase\AEC\sybsystem\master.dat" -sAEC
                     -e"J:\sybase\AEC\ASE-15_0\install\AEC.log"
                     -i"J:\sybase\AEC\ini" -M"J:\sybase\AEC\ASE-15_0" '.
03/13/15 06:23:55 AM Calling the shell with '0 = return code.'.
03/13/15 06:24:11 AM Calling the shell with
                     '"J:\sybase\AEC\ASE-15_0\bin\sqlsrvr.exe"
                     -d"J:\sybase\AEC\sybsystem\master.dat" -sAEC
                     -e"J:\sybase\AEC\ASE-15_0\install\AEC.log"
                     -i"J:\sybase\AEC\ini" -M"J:\sybase\AEC\ASE-15_0" '.
03/13/15 06:24:11 AM waiting for server 'AEC' to boot...
03/13/15 06:24:21 AM SERVER ERROR: Failed to boot server 'AEC'.
03/13/15 06:24:21 AM SERVER ERROR: Couldn't reboot server 'AEC' after changing
                     internal tables.
03/13/15 06:24:25 AM CONNECTIVITY ERROR: Open Client message: 'ct_connect():
                     network packet layer: internal net library error: Net-Lib
                     protocol driver call to connect two endpoints failed
                     Failed to connect to the server - Error is 10061 No
                     connection could be made because the target machine
                     actively refused it.

                    
                     '.
03/13/15 06:24:25 AM CONNECTIVITY ERROR: Initialization of auditinit
                     connectivity module failed.
03/13/15 06:24:25 AM Task failed: set the default character set and/or default
                     sort order for the Adaptive Server. Terminating
                     configuration.
03/13/15 06:24:25 AM Configuration failed.
03/13/15 06:24:25 AM Exiting.
03/13/15 06:24:25 AM The log file for this session is
                     'J:\sybase\AEC\ASE-15_0\init\logs\log0313.007'.
03/13/15 06:24:25 AM Log close.

Install Log

00:0000:00000:00000:2015/03/13 06:24:13.07 kernel  SySAM: Using licenses from: J:\sybase\AEC\\SYSAM-2_0\licenses\SYBASE.lic;J:\sybase\AEC\\SYSAM-2_0\licenses\SYBASE_ASE_DE.lic

00:0000:00000:00000:2015/03/13 06:24:13.70 kernel  SySAM: Checked out license for 2 ASE_CORE (2020.1231/permanent/100C 0F04 3F88 1821).

00:0000:00000:00000:2015/03/13 06:24:13.70 kernel  This product is licensed to: SAP, for use with SAP Business Applications.

00:0000:00000:00000:2015/03/13 06:24:13.70 kernel  Checked out license ASE_CORE

00:0000:00000:00000:2015/03/13 06:24:13.70 kernel  Adaptive Server Enterprise (Enterprise Edition)

00:0000:00000:00000:2015/03/13 06:24:13.71 kernel  Using config area from primary master device.

00:0000:00000:00000:2015/03/13 06:24:13.71 kernel  Warning: Using default file 'J:\sybase\AEC\AEC.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.

00:0000:00000:00000:2015/03/13 06:24:13.73 kernel  Allocating a shared memory segment of size 131137536 bytes.

00:0000:00000:00000:2015/03/13 06:24:13.73 kernel  WARNING: shared memory segment is being held by another application

00:0000:00000:00000:2015/03/13 06:24:13.75 kernel  FATAL: shared memory region is being held at 131104768 bytes but 131137536 bytes are required

00:0000:00000:00000:2015/03/13 06:24:13.75 kernel  kbcreate: couldn't create kernel region.

00:0000:00000:00000:2015/03/13 06:24:13.75 kernel  kistartup: could not create shared memory

Best

Martin

After implementing solution in Note 2011550 - SYB: SAP ASE on Windows fails to start, issue was fixed

Hello,

In Adaptive Server Enterprise 15.7 ESD #2> New Features Guide Adaptive Server Enterprise 15.7 ESD #2> Chapter 9: Concurrent dump database and dump transaction Commands, it is mentioned that

"It may be difficult to determine whether a transaction log you dumped with dump tran precedes the database dump (in which case it need not be loaded), or occurs after the database dump (in which case it should be loaded). Use the dump history file to resolve questions of precedence by including the transaction log or not, as appropriate."

So it appears that the dump history file contains the information related to which transaction log dump belongs to which full dump.

However, by following the testing procedure in this article (Test of Enhancements to Dump and Load in ASE15.7 ESD#2 - Sybase), I found out that the first timestamp in each line of the history file shows the last log dump time for full/log dump, and the third timestamp shows the start time of the full/log dump.

Since there is no timestamp showing the dump instant for a full dump, my questions are: how is the history file useful in resolving the potential issues with concurrent full and transaction log dumps? And how is sybrestore tool able to resolve this?

The steps that I followed are below:

1. First create a table test_table in database ali_db_1, and add a row at 12:02PM. So 12:02 is the last modification time for this database.

1. Do a full dump which starts at 12:03:16 and completes at 12:03:18. Dump instant (from the backup server log) is 12:03:18.

1. Now, see what dumphist looks like. The first timestampshows the last transaction log dump time (Mar 3 1:18:27). The 3^rd timestamp shows the time full dump started.

2|4|ali_db_1|2|Mar  3 2015  1:18:27:980PM|Mar  3 2015 1:18:27:980PM|Mar 10 2015 12:03:15:596PM|/opt/sybsp103/tempdump/ali_db_1.DB.20150310.120316.000|4863|*|0|0|1

1. Add another row in the table at 12:06PM.

1. Add another row in the table at 12:07PM. So 12:07 is the last modification time for this database.

1. Do a transaction log dump which starts at 12:08:21 and finishes at the same second.

1. Now, see what dumphist looks like. The first timestamp shows the last transaction log dump time (Mar 3 1:18:27). The 3^rd timestamp shows the time log dump started.

3|4|ali_db_1|2|Mar  3 2015  1:18:27:980PM|Mar 10 2015 12:08:21:183PM|Mar 10 2015 12:08:21:183PM|/opt/sybsp103/tempdump/ali_db_1.TRAN.20150310.120821.000|0|*|0|0|1

1. Add another row in the table at 12:10PM. So 12:10 is the last modification time for this database.

1. Do another log dump which starts at 12:10:44 and finishes at the same second.

1. Now, see what dumphist looks like. The first timestamp shows the last log dump time (12:08:21PM). The 3^rd timestamp shows the time log dump started.

3|4|ali_db_1|2|Mar 10 2015 12:08:21:183PM|Mar 10 2015 12:10:44:753PM|Mar 10 2015 12:10:44:753PM|/opt/sybsp103/tempdump/ali_db_1.TRAN.20150310.121044.000|0|*|0|0|1

Take a look at the "sp_dump_history" stored procedure to see that there are record types in the history file (2=dumpdb).  THis should help explain the sequence of events that can lead to recovery and troubleshooting.

Hi,

thank you for you help. So.... the problem is on saptools dataabse only... is it true? So, I don't know when exactly born this problem... so, can I rebuild saptools database from begin? ... there is any script? How can I destroy and recreate saptools dataabse?

Thank you.

• Checking table 'DBH_SNAP_CACHEDOBJECTS' (object ID 249048892): Logical page size is 16384 bytes.
• Checking partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) of table 'DBH_SNAP_CACHEDOBJECTS'. The logical page size of this table is 16384 bytes.
• The total number of data pages in partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) is 121.
• Partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) has 1019 data rows.
• The total number of empty pages (with all deleted rows) in partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) is 1.
• The total number of pages in partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) which could be garbage collected to free up some space is 120.
• The total number of deleted rows in partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) is 20462.
• The total number of pages in partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) with more than 50 percent garbage is 120.
• The total number of pages in partition 'DBH_SNAP_CACHEDOBJECTS_249048892' (partition ID 249048892) with more than 50 percent insert free space is 121.
• The total number of data pages in this table is 121.
• The total number of empty pages (with all deleted rows) in this table is 1.
• The total number of pages which could be garbage collected to free up some space is 120.
• The total number of deleted rows in the table is 20462.
• The total number of pages with more than 50 percent garbage is 120.
• The total number of pages with more than 50 percent insert free space is 121.
• Table has 1019 data rows.
• DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.
• Execution time: 0.313 seconds

• Checking table 'DBH_STG_SPINLOCKACTVTY' (object ID 1452529177): Logical page size is 16384 bytes.
• Checking partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) of table 'DBH_STG_SPINLOCKACTVTY'. The logical page size of this table is 16384 bytes.
• The total number of data pages in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) is 2.
• Partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) has 300 data rows.
• Partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) has 59 row-level only compressed rows, and 241 page-level compressed rows.
• The total number of page-level compressed pages in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) is 1.
• The total number of empty pages (with all deleted rows) in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) is 0.
• The total number of pages in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) which could be garbage collected to free up some space is 0.
• The total number of deleted rows in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) is 0.
• The total number of pages in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) with more than 50 percent garbage is 0.
• The total number of pages in partition 'DBH_STG_SPINLOCKACTVTY_1452529177' (partition ID 1452529177) with more than 50 percent insert free space is 1.
• The total number of data pages in this table is 2.
• The total number of pages with more than 50 percent insert free space is 1.
• The total number of page-level compressed pages in this table is 1.
• Table has 59 row-level only compressed rows, and 241 page-level compressed rows.
• Table has 300 data rows.
• DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.
• Execution time: 0.016 seconds

Ganimede,

Please refer the below scripts:

• 1611715   SYB: How to restore a Sybase ASE database server (Windows)
• 1618817   SYB: How to restore a Sybase ASE database server (UNIX)

Regards

Kiran K Adharapuram

OK... but I'm not sure when problem starts... so, can I recreate an empty saptools database?