- 论坛徽章:
- 0
|
以下是运行的出错信息，请教解决方案
>; C:SybaseServer>;isql -Usa -P<zmis.sql
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the table 'N006', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 4:
>; Cannot drop the table 'N009', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 4:
>; Cannot drop the table 'N010', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 4:
>; Cannot drop the table 'N120', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 4:
>; Cannot drop the table 'X301', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the table 'X302', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the table 'X303', because it doesn't exist in the system catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 1:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Success
>;
>;
>;
>; C:SybaseServer>;isql -Usa -P<account.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_AutoAccount', because it doesn't exist in the
>; system catalogs.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_AutoAccount', Line 6:
>; Incorrect syntax near '/'.
>;
>; C:SybaseServer>;isql -Usa -P<p_bs_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_BS_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BS_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BS_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BS_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BS_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BS_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_by_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_BY_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BY_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BY_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BY_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BY_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_BY_HD', Line 62:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_cb.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_CB', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CB', Line 161:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CB', Line 161:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CB', Line 161:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CB', Line 161:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CB', Line 161:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_cgjh_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_CGJH_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CGJH_HD', Line 59:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CGJH_HD', Line 59:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CGJH_HD', Line 59:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CGJH_HD', Line 59:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_CGJH_HD', Line 59:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_copydata.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_CopyData', because it doesn't exist in the system
>; catalogs.
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 5:
>; jdcbak.dbo.X101 not found. Specify owner.objectname or use sp_help to check
>; whether the object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 5:
>; jdcmis.dbo.X101 not found. Specify owner.objectname or use sp_help to check
>; whether the object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 12:
>; jdcbak.dbo.X102 not found. Specify owner.objectname or use sp_help to check
>; whether the object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 12:
>; jdcmis.dbo.X102 not found. Specify owner.objectname or use sp_help to check
>; whether the object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 33:
>; X301 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 44:
>; X302 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 51:
>; X303 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 58:
>; X302 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 58:
>; X301 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 69:
>; X303 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 69:
>; X301 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 80:
>; N006 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 86:
>; N006 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 86:
>; V_QWJ_G02309 not found. Specify owner.objectname or use sp_help to check whethe
r
>;
>; the object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_CopyData', Line 86:
>; V_QWJ_G02310 not found. Specify owner.objectname or use sp_help to check whethe
r
>;
>; the object exists (sp_help may produce lots of output).
>;
>; C:SybaseServer>;isql -Usa -P<p_cprk_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_CPRK_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 137, Level 15, State 2:
>; Procedure 'P_CPRK_HD', Line 50:
>; Must declare variable '@k12402'.
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_cw_yszz.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_CW_YSZZ', because it doesn't exist in the system
>; catalogs.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 25:
>; Incorrect syntax near '@maxtable'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 38:
>; Incorrect syntax near '@maxtable'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 43:
>; Incorrect syntax near '@maxtable'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 50:
>; Incorrect syntax near '@maxtable'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 52:
>; Incorrect syntax near '@maxtable'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 58:
>; Incorrect syntax near '@maxtable'.
>; Msg 156, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 67:
>; Incorrect syntax near the keyword 'if'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 68:
>; Incorrect syntax near '@maxtable'.
>; Msg 195, Level 15, State 5:
>; Procedure 'P_CW_YSZZ', Line 68:
>; 'T5' is not a recognized option.
>; Msg 195, Level 15, State 5:
>; Procedure 'P_CW_YSZZ', Line 70:
>; 'T5' is not a recognized option.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 79:
>; Incorrect syntax near '@maxtable'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_CW_YSZZ', Line 79:
>; Incorrect syntax near '@maxtable'.
>;
>; C:SybaseServer>;isql -Usa -P<p_db_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_DB_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 208, Level 16, State 1:
>; Procedure 'P_DB_HD', Line 23:
>; D101 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_DB_HD', Line 27:
>; D101 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Procedure 'P_DB_HD', Line 40:
>; D102 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_gz_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_GZ_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_GZ_HD', Line 92:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_GZ_HD', Line 92:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_GZ_HD', Line 92:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_GZ_HD', Line 92:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_GZ_HD', Line 92:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>; C:SybaseServer>;isql -Usa -P<p_hy_hz.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_HY_HZ', because it doesn't exist in the system
>; catalogs.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_HY_HZ', Line 22:
>; Incorrect syntax near '/'.
>; Msg 102, Level 15, State 1:
>; Procedure 'P_HY_HZ', Line 28:
>; Incorrect syntax near '/'.
>;
>; C:SybaseServer>;isql -Usa -P<p_jh_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_JH_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_JH_HD', Line 77:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_JH_HD', Line 77:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_JH_HD', Line 77:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_JH_HD', Line 77:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_JH_HD', Line 77:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>; C:SybaseServer>;isql -Usa -P<p_ll_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_LL_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 137, Level 15, State 2:
>; Procedure 'P_LL_HD', Line 50:
>; Must declare variable '@k12002'.
>;
>; C:SybaseServer>;isql -Usa -P<p_pd_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_PD_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_PD_HD', Line 81:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_PD_HD', Line 81:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_PD_HD', Line 81:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_PD_HD', Line 81:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_PD_HD', Line 81:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>; C:SybaseServer>;isql -Usa -P<p_sj_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_SJ_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_SJ_HD', Line 22:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_SJ_HD', Line 22:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_SJ_HD', Line 22:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_SJ_HD', Line 22:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_SJ_HD', Line 22:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>;
>; C:SybaseServer>;isql -Usa -P<p_th_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_TH_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_TH_HD', Line 63:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_TH_HD', Line 63:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_TH_HD', Line 63:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_TH_HD', Line 63:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_TH_HD', Line 63:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>; C:SybaseServer>;isql -Usa -P<p_tl_hd.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_TL_HD', because it doesn't exist in the system
>; catalogs.
>; Msg 137, Level 15, State 2:
>; Procedure 'P_TL_HD', Line 50:
>; Must declare variable '@k12202'.
>;
>; C:SybaseServer>;isql -Usa -P<修改负库存.sql
>; Msg 3701, Level 11, State 1:
>; Line 1:
>; Cannot drop the procedure 'P_ModifyLowKC', because it doesn't exist in the
>; system catalogs.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_ModifyLowKC', Line 56:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_ModifyLowKC', Line 56:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_ModifyLowKC', Line 56:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_ModifyLowKC', Line 56:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Procedure 'P_ModifyLowKC', Line 56:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system'
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>;
>;
>; C:SybaseServer>;isql -Usa -P<view.sql
>; Msg 911, Level 11, State 2:
>; Line 1:
>; Attempt to locate entry in sysdatabases for database 'zmis' by name failed - n
>; entry found under that name. Make sure that name is entered properly.
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the view 'V_QWJ_YHD', because it doesn't exist in the system
>; catalogs.
>; Msg 208, Level 16, State 1:
>; Line 4:
>; N010 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 208, Level 16, State 1:
>; Line 4:
>; N006 not found. Specify owner.objectname or use sp_help to check whether the
>; object exists (sp_help may produce lots of output).
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the view 'V_QWJ_KCCX', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the view 'V_QWJ_G02309', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 3701, Level 11, State 1:
>; Line 3:
>; Cannot drop the view 'V_QWJ_G02310', because it doesn't exist in the system
>; catalogs.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment.
>; Msg 1105, Level 17, State 3:
>; Line 3:
>; Can't allocate space for object 'syslogs' in database 'master' because 'system
>; segment is full/has no free extents. If you ran out of space in syslogs, dump
>; the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>; increase size of the segment. |
|
免费注册
发表于 2003-08-07 20:26
