cancel
Showing results for 
Search instead for 
Did you mean: 

SQL0968C The file system is full. SQLSTATE=57011 during EXPORT

Former Member
0 Kudos

Hi Experts

          We are facing the error SQL0968C  The file system is full.  SQLSTATE=57011 during the EXPORT of the System. The log for the package which is  failed  as shown

LOG:

/usr/sap/PR3/SYS/exe/run/R3load: START OF LOG: 20150415023459

/usr/sap/PR3/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP

/usr/sap/PR3/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Dec 12 2009 04:42:01

/usr/sap/PR3/SYS/exe/run/R3load -e BSIS.cmd -datacodepage 4102 -l BSIS.log -stop_on_error

(DB) INFO: connected to DB

(DB) INFO: Export without hintfile

(GSI) INFO: dbname   = "PR3                                                                                                                             "

(GSI) INFO: vname    = "DB6                             "

(GSI) INFO: hostname = "UNKNOWN                                                         "

(GSI) INFO: sysname  = "HP-UX"

(GSI) INFO: nodename = "prqr3"

(GSI) INFO: release  = "B.11.23"

(GSI) INFO: version  = "U"

(GSI) INFO: machine  = "ia64"

(GSI) INFO: instno   = "0020260282"

(EXP) ERROR: DbSlExeRead failed

  rc = 99, table "BSIS"

  (SQL error -968)

  error message returned by DbSl:

SQL0968C  The file system is full.  SQLSTATE=57011

(DB) INFO: disconnected from DB

/usr/sap/PR3/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/PR3/SYS/exe/run/R3load: END OF LOG: 20150415032219

Accepted Solutions (1)

Accepted Solutions (1)

former_member182657
Active Contributor
0 Kudos

Hi,

SQL0968C  The file system is full

Have you checked space at OS level & table spaces,If required try to extend table space if any & retry the process again.

Good luck !!

Former Member
0 Kudos

Hi Gaurav Rana

       Thanks for fast reply.

           We checked at os level we have spaces. The following was the output when i go for df -b command

# df -b

/db2                  (/dev/vg01/lvol5       ) :  1909661 Kbytes free

/home               (/dev/vg01/lvol6       ) : 10318228 Kbytes free

/opt                   (/dev/vg01/lvol7       ) :  5254704 Kbytes free

/tmp                  (/dev/vg01/lvol8       ) :  9621318 Kbytes free

/usr                   (/dev/vg01/lvol9       ) :  5196303 Kbytes free

/var                   (/dev/vg01/lvol10      ) : 17278600 Kbytes free

/stand                (/dev/vg01/lvol1       ) :  1943738 Kbytes free

/                        (/dev/vg01/lvol4       ) : 19097424 Kbytes free -----------export directory location

After that When i go for command "db2 list tablespaces show detail" i found that the following tablespaces which are got fulled. The log was as follows

Tablespace ID                        = 3

Name                                   = PSAPTEMP16

Type                                 = System managed space

Contents                             = System Temporary data

State                                = 0x0000

Detailed explanation:

Normal

Total pages                          = 1

Useable pages                        = 1

Used pages                           = 1

Free pages                           = Not applicable

High water mark (pages)              = Not applicable

Page size (bytes)                    = 16384

Extent size (pages)                  = 2

Prefetch size (pages)                = 2

Number of containers                 = 1

----------------------------------------

Tablespace ID                        = 4

Name                                 = SYSTOOLSTMPSPACE

Type                                 = System managed space

Contents                             = User Temporary data

State                                = 0x0000

   Detailed explanation:

     Normal

Total pages                          = 1

Useable pages                        = 1

Used pages                           = 1

Free pages                           = Not applicable

High water mark (pages)              = Not applicable

Page size (bytes)                    = 16384

Extent size (pages)                  = 2

Prefetch size (pages)                = 2

Number of containers                 = 1

Thanks & Regards

MANIKANTA

former_member182657
Active Contributor
0 Kudos

Hi Manikanta,

Suggest you to check with SAP Note  365314 - DB2 UDB for AIX: User Limits for db2<sid>/<sid>adm

1099936 - DB6: SQL0670N The row length of a table exceeds 4005 bytes

Additionally do check for any space quotas on your system with a complete restart of system.

Regards,

Answers (3)

Answers (3)

former_member182657
Active Contributor
0 Kudos

Hi Manikanta,

Have your issue been resolved ? If yes kindly close the thread or update the same.

Regards,

former_member182657
Active Contributor
0 Kudos

ADM6017E  The table space "PSAPTEMP16" (ID "3") is full. Detected on

          container "/db2/PR3/saptemp1/NODE0000/temp16/PSAPTEMP16.container000"

You need to check with SAP Note   334608 - DB6: SMS tablespace ##(PSAPTEMP##) is FULL

Hope this will resolve your issue.

Good luck !!

former_member182657
Active Contributor
0 Kudos

In addition check with siimilar thread

Former Member
0 Kudos

Hi Gaurav

      We found that our PSAPTEMP16 tablespace which is SYSTEM MANAGED size was full. we saw it on db2diag.log file

So can we increase PSAPTEMP16 tablespace. If yes please tell me the command. The log was

MESSAGE : ADM6017E  The table space "PSAPTEMP16" (ID "3") is full. Detected on

          container "/db2/PR3/saptemp1/NODE0000/temp16/PSAPTEMP16.container000"

          (ID "0").  The underlying file system is full or the maximum allowed

          space usage for the file system has been reached. It is also possible

          that there are user limits in place with respect to maximum file size

          and these limits have been reached.


Thanks & Regards

MANIKANTA

former_member182657
Active Contributor
0 Kudos

Hi Manikanta,

Could you check with SCN thread

Regards,

former_member185954
Active Contributor
0 Kudos

Hello Manikanta,

While performing export, the system copy guide has a standard suggestion about size of your temporary tablespace, which is normally a percentage of size of your DB.

Nobody can tell you how much you should maintain, however you can monitor its usage during export using DB tools to see that its contents grow and shrink depending on the how many parallel processes you start during export and how big packages are.

Explore this area first before restarting your export by simply fixing this issue.

Good luck.

Regards,

Siddhesh