Archive

Posts Tagged ‘Scratch Database’

ASE Archive Databases for Compressed Backup.

March 12th, 2011 No comments

Observation:

1. For compressed backup , only works with option : with compression=””

2. If we have taken the backup with with compression=”” option, we no need to specify the the compression level during load database.

3. We can perform the dbcc on recent dump files of the databases, without hampering the performance of the prodduction database.

4. We can also object level recovery using the Archive Database.

5. For mapping the dump stipes , it makes sysaltusages table in scratch database.

Testing:

1> dump database test_db to “/data/sybase/testing_host/dump/test_db.dmp1″
2> stripe on “/data/sybase/testing_host/dump/test_db.dmp2″ with compression=”4″
3> go
Backup Server session id is: 131. Use this value when executing the ‘sp_volchanged’ system stored procedure after fulfilling any
volume change request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file /data/sybase/testing_host/dump/test_db.dmp1.
Backup Server: 4.41.1.1: Creating new disk file /data/sybase/testing_host/dump/test_db.dmp2.
Backup Server: 6.28.1.1: Dumpfile name ‘sr_load1106806A97′ section number 1 mounted on disk file
‘/data/sybase/testing_host/dump/test_db.dmp2′
Backup Server: 6.28.1.1: Dumpfile name ‘sr_load1106806A97′ section number 1 mounted on disk file
‘/data/sybase/testing_host/dump/test_db.dmp1′
Backup Server: 4.188.1.1: Database test_db: 11960 kilobytes (4%) DUMPED.
Backup Server: 4.188.1.1: Database test_db: 29094 kilobytes (6%) DUMPED.
Backup Server: 4.188.1.1: Database test_db: 315648 kilobytes (100%) DUMPED.
Backup Server: 4.188.1.1: Database test_db: 323870 kilobytes (100%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database test_db: 323884 kilobytes (100%) DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database test_db).
1> !!ls -ltr /data/sybase/testing_host/dump/test_db.dmp*
[sh:ls -ltr /data/sybase/testing_host/dump/test_db.dmp*]
-rw-r—– 1 sybase dba 40783872 Mar 9 07:35 /data/sybase/testing_host/dump/test_db.dmp1
-rw-r—– 1 sybase dba 41261056 Mar 9 07:35 /data/sybase/testing_host/dump/test_db.dmp2

1> create database scratch on data16=’100M’ log on log01=’100M’
2> go
CREATE DATABASE: allocating 51200 logical pages (100.0 megabytes) on disk ‘data16′.
CREATE DATABASE: allocating 51200 logical pages (100.0 megabytes) on disk ‘log01
Database ‘scratch’ is now online.

1> sp_dboption ‘scratch’,”scratch database”, “true”
2> go
Database option ‘scratch database’ turned ON for database ‘scratch’.
Running CHECKPOINT on database ‘scratch’ for option ‘scratch database’ to take e
(return status = 0)

1> use scratch
2> go
1> checkpoint
2> go
1> use master
2> go

1> sp_configure ‘compression memory size’
2> go
Parameter Name Default Memory Used Config Value Run Value Unit
Type
—————————— ——————– ———– ——————– ——————– ——————–
———-
compression memory size 0 152 0 0 memory pages(2k)
dynamic
(1 row affected)
(return status = 0)
1> sp_configure ‘compression memory size’,64
2> go
Parameter Name Default Memory Used Config Value Run Value Unit
Type
—————————— ——————– ———– ——————– ——————– ——————–
———-
compression memory size 0 280 64 64 memory pages(2k)
dynamic
(1 row affected)

1> create archive database archivedb
2> on data15=’50M’
3> with scratch_database = scratch
4> go
CREATE DATABASE: allocating 25600 logical pages (50.0 megabytes) on disk ‘data15′.

1> load database archivedb from “/data/sybase/testing_host/dump/test_db.dmp1″
2> stripe on “/data/sybase/testing_host/dump/test_db.dmp2″
3> go

1> load database archivedb from “/data/sybase/testing_host/dump/test_db.dmp1″
2> stripe on “/data/sybase/testing_host/dump/test_db.dmp2″
3> go
Started estimating recovery log boundaries for database ‘archivedb’.
Database ‘archivedb’, checkpoint=(303154, 21), first=(303154, 21), last=(303155, 6).
Completed estimating recovery log boundaries for database ‘archivedb’.
Started ANALYSIS pass for database ‘archivedb’.
Completed ANALYSIS pass for database ‘archivedb’.
Started REDO pass for database ‘archivedb’. The total number of log records to process is 11.
Redo pass of recovery has processed 2 committed and 0 aborted transactions.
Completed REDO pass for database ‘archivedb’.
Use the ONLINE DATABASE command to bring this database online; ASE will not bring it online automatically.
1> online database archivedb
2> go
Started estimating recovery log boundaries for database ‘archivedb’.
Database ‘archivedb’, checkpoint=(303154, 21), first=(303154, 21), last=(303155, 6).
Completed estimating recovery log boundaries for database ‘archivedb’.
Started ANALYSIS pass for database ‘archivedb’.
Completed ANALYSIS pass for database ‘archivedb’.
Recovery of database ‘archivedb’ will undo incomplete nested top actions.
Database ‘archivedb’ is now online.
1> use archivedb
2> go
1> set rowcount 5
2> go
1> select name from sysobjects where type=’U’
2> go
name
—————————————————————————————————————————————————————————————————————————————————————
testing_FPOSDailyFunding
testing_IDeltaContracts
testing_RMSRates
testing_ESSPLFXRpt
testing_ESSAlgo
(5 rows affected)
1> set rowcount 0
2> go
1> select * from sysaltusages where 1=2
2> go
dbid location lstart size vstart vdevno segmap
—— ———– ———– ———– ———– ———– ———–
(0 rows affected)
1> set rowcount 5
2> go
1> select * from sysaltusages
2> go
dbid location lstart size vstart vdevno segmap
—— ———– ———– ———– ———– ———– ———–
8 4 0 256000 1 24 3
8 4 256000 51200 1 24 4
8 4 307200 256000 1 24 3
8 5 0 32 42 26 3
8 5 32 32 51 26 3
(5 rows affected)