Dear Mr Almanza
The device 'QAS_LOG_001' does have now three 'fragments. All the fragments belong to database QAS .
However, one of the fragments is a 'default/data' segment and will be used by the database for storing system and user tables - but not the transaction log.
It is not a big problem - more a cosmetic issue. If you created the device files for 'log' on a seprate file system with high speed / mirroired disk - then some of this space is now 'wasted' to store ordinary user tables instead of the transaction log.
To correct this:
DUMP the database QAS,
DROP and RECREATE database QAS with the same layout except that the data fragment on QAS_log_001 gets created on 'QAS_data_001' and then load the dump you took earlier.
Once you dumped the database you may use the command
LOAD DATABASE QAS WITH LISTONLY = 'CREATE_SQL'
to obtain a DDL for the database which you may save and edit as needed. (assuming ASE is 15.7.0.020 or higher)
You may also use the shrink database feature which is available in newer ASE releases
! Attention: The 'Shrink database' feature is supported fo SAP only as of 15.7 SP110.
See details in ASE online documentation.
Do take a full DUMP of the database directly after using the shrink database feature !
With kind regards
Tilman Model-Bosch