Data & Log Segments sharing the same device

Data & Log Segments sharing the same device

Post by Wendy Perr » Fri, 22 Mar 1996 04:00:00



You can use the sp_logdevice stored procedure to move the log.

sp_logdevice dbname, device_name
go

This will place all future allocations of syslogs on the new device.

 
 
 

Data & Log Segments sharing the same device

Post by Michael Sweetma » Fri, 22 Mar 1996 04:00:00


When restoring a database dump, the destination database must have the EXACT
structure as the source database.  This not only means the total size of data
and log segments, but the order and size of each individual device!  If this is
not the case, the load database will make it so.

If you have the drive space, create two databases on the same server and use
statements like:
   insert destinationdb.owner.tablename
    select * from sourcedb.owner.tablename

to move the data sans bcp.

-Mike S.

 
 
 

Data & Log Segments sharing the same device

Post by FTsabed » Fri, 22 Mar 1996 04:00:00


We are currently using Sybase v10 on HP Unix 9.0.5.  Several of our
database have been created with data and log configured on the same
device.  As a result, our transaction logs have been constantly filling
up, requiring "dump tran <database_name> with no_log.  Our transaction
logs are not required for recovery.  

Is there any way in which to separate the data and log segments so that
they physically utilize separate devices.  I did take one database, made a
dump of it,  dropped the database, recreated the databae so that the data
segment and log segment were configured on separate devices, and reloaded
the database from the dump.  To no avail.  The log segment is on the
device supposedly only created for data.

Any suggestions would be greatly appreciated.  What I'm trying to avoid is
having to bcp out all the tables, recreate the database appropriately, and
bcp back in the tables.  --- a very time-consuming process.


     or


    or


Thanks in advance!

 
 
 

Data & Log Segments sharing the same device

Post by Chiu Wen-Sh » Sun, 24 Mar 1996 04:00:00


disk init......

alter database your_db on new_device

sp_logdevice new_device

: We are currently using Sybase v10 on HP Unix 9.0.5.  Several of our
: database have been created with data and log configured on the same
: device.  As a result, our transaction logs have been constantly filling
: up, requiring "dump tran <database_name> with no_log.  Our transaction
: logs are not required for recovery.  

: Is there any way in which to separate the data and log segments so that
: they physically utilize separate devices.  I did take one database, made a
: dump of it,  dropped the database, recreated the databae so that the data
: segment and log segment were configured on separate devices, and reloaded
: the database from the dump.  To no avail.  The log segment is on the
: device supposedly only created for data.

: Any suggestions would be greatly appreciated.  What I'm trying to avoid is
: having to bcp out all the tables, recreate the database appropriately, and
: bcp back in the tables.  --- a very time-consuming process.


:                                                                          
:      or
:                                                                  

:                                                                          
:     or
:                                                                  

: Thanks in advance!

--

Regards,
Kelvin

 
 
 

1. log segments on data devices

We recently setup a new Sybase 11.5.1 server on Solaris 2.6. We created
separate data and log database devices on raw partitions. We created
some new databases and migrated several databases from other servers
using dump/restore. When we run sp_helpdb it reports that two of the
migrated databases have log segments on the database devices meant for
data. (They also have log segments on their associated log database
devices.) This appears to have been propagated through the dump/restore.

Sybase says the only way to correct this condition is to bcp out all the
tables, drop the database, recreate it, and bcp the data back in. The
databases in question have a lot of tables, making this solution
undesirable.

Is there an alternative solution to this problem?

Thanks and regards, Chris Keller

2. ISDN Changes IP Address - lose connection

3. How do you share log and data on one device

4. ***Dallas, Tx - Paradox Programmer***

5. Data & Log Device Space

6. Accessing Data in VFP

7. Data & Log Device Space Available

8. PFW 5.0 and Excel 5.0 DDE

9. changing tempdb device to log & data

10. Log segments in master device

11. i'dont know the device sizes, I've data device & log device , how to get data back to a new database

12. Moving the log from a log and data device

13. Q: Converting LOG ONLY devices to DATA AND LOG