PSAPTEMP Tablespace in ECC6.0

Dear all,
After upgrading from 4.6c to ECC6.0, we found that the tablespace PSAPTEMP is quite different from the other tablespaces.
Given below is the brtools output of the tablespaces:
Pos.  Tablespace     Type  Status    ExtMan.  SegMan.  Backup  Files/AuExt.
      Total[KB]   Used[%]    Free[KB]  MaxSize[KB]  ExtSize[KB]  FreeExt.    Largest[KB]
45 - PSAPSTABI      DATA  ONLINE    LOCAL    MANUAL    NO         2/0
      16777216     85.04     2509248     16777216            0       264      664576:656384:262080:262080:109568
46 - PSAPTEMP       TEMP  ONLINE    LOCAL    MANUAL    NO         1/0
       9216000      0.00     9216000      9216000            0         0           0:0:0:0:0
47 - PSAPUNDO       UNDO  ONLINE    LOCAL    MANUAL    NO         5/0
       6725632      0.00     6725312      6725632            0       842      290816:287744:142336:139200:95232
PSAPTEMP alone has the last field as 0:0:0:0:0.
1. Do we need to modify/alter the psaptemp tablespace to be normal?
2. How do we assign the correct size of the PSAPTEMP tablespace to our environment?
Thanks & Regards
Senthil

Thanks Sudha for replying:
I tryed to refresh the db02 and it schedules a background job:
Job log overview for job:    REFRESH SPACE STATISTIC:DEFAULT / 08532100                                                                               
Date       Time     Message text                                                                Message class Message no. Message type                                                                               
12/20/2007 08:53:22 Job started                                                                      00           516          S         
12/20/2007 08:53:22 Step 001 started (program RSORACOLR, variant &0000000000000, user ID LDING)      00           550          S         
12/20/2007 08:53:22 Job finished                                                                     00           517          S                                                                               
But the background job finished successfully, but without collecting statistics
Regards
Senthil

Similar Messages

  • My PSAPTEMP tablespace always show 100% Full or Used

    Dear All ,
    Using brtools my tablespace PSAPTEMP always show 100% full or Used, I extend 2 Gb size in PSAPTEMP tablespace but still no solution
    Please guide me why it always shows 100% used and what is the performance impact on that
    Regards
    Shahid

    Hello Shahid,
    > Please guide me why it always shows 100% used and what is the performance impact on that
    This is a normal behaviour in case of a temporary tablespace.
    If you do sorts, hash-joins, etc. which can not be done in memory-only you allocate extents in the temporary tablespace. If you finish your query, that temporary extents will be marked as free but they still kept allocated. So over the uptime of your database your temporary tablespace will be filled by allocated (but marked as free) extents .. and so you will see it as "full". You can also check the current "real" usage of your temporary tablespace by the view V$TEMPSEG_USAGE:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2164.htm#i1421319
    The temporary extents will be deallocated by a database shutdown or by a database start, if the database crashed before.
    If you don't get any ORA-01652 by your query .. everything is fine.
    Regards
    Stefan

  • PSAPTEMP tablespace

    HI all,
    I am trying  to run an Import of the client and its getting stuck, so before running the import i started the Database Optimizer Statistics and when i checked the system log i was getting ORA-25153: Temporary Tablespace is Empty and then i checked DB02 and saw PSAPTEMP did not have any space allocated ,as i have restored this system and created a new Control file , so in the process the PSAPTEMP tablespace has affected.
    PSAPTEMP     0,00     0,00     0     NO     0,00     0,00     0     0     0     0     ONLINE     TEMPORARY
    Can someone please help me resolve this issue.
    Thanks

    Hi Shambo,
    Good news is that , the job has finished and it has updated the PSAPTEMP (thanks to u).
    PSAPSR3     41.020,00     16,94     100     YES     200.000,00     158.996,94     21     20     156.893     197.589     ONLINE     PERMANENT
    PSAPSR3700     55.480,00     266,13     100     YES     160.000,00     104.786,13     35     16     801     10.599     ONLINE     PERMANENT
    PSAPSR3USR     20,00     18,13     9     YES     10.000,00     9.998,13     0     1     29     29     ONLINE     PERMANENT
    PSAPTEMP     2.120,00     2.120,00     0     YES     10.000,00     10.000,00     0     1     0     0     ONLINE     TEMPORARY
    PSAPUNDO     9.120,00     8.966,56     2     YES     10.000,00     9.846,56     2     1     11     34     ONLINE     UNDO
    SAPTEMP     10.500,00     10.500,00     0     NO     10.500,00     10.500,00     0     1     0     0     ONLINE     TEMPORARY
    SYSAUX     260,00     19,31     93     YES     10.000,00     9.759,31     2     1     875     1.810     ONLINE     PERMANENT
    SYSTEM     840,00     7,13     99     YES     10.000,00     9.167,13     8     1     1.204     2.768     ONLINE     PERMANENT
    But i think , trying this process , i have created another SAPTEMP temporary Tablespace as well, Should i leave it like that , or delete it , can u pls tell me how would i delete it.
    For the size of PSAPTEMP tablespace , i have used the size that u sent me and not the one that I have sent u from Control trace file..just FYI only..
    Thanks for help..

  • Tablespace: PSAPTEMP # Tablespace files autoextend can cause file system overflow

    Hi All,
    We are seeing the above message after updating the kernel from 701 SP 125 to 720 SP 600.
    I have checked the data files that make up PSAPTEMP and none are set to auto extend so I am confused as to what it is complaining about.
    Tablespace name
    Size(MB)
    Free(MB)
    Used(%)
    Autoextend
    Total size(MB)
    Total free space(MB)
    Total used (%)
    #Files
    #Segments
    #Extents
    Status
    Contents
    Compression
    PSAPTEMP
    11,264.00
    11,262.00
    0
    NO
    11,264.00
    11,262.00
    0
    6
    0
    0
    ONLINE
    TEMPORARY
    DISABLED
    File name
    File Id
    Tablespace name
    Size(MB)
    #Blocks
    Status
    Rel. file number
    Autoextensible
    Maxsize(MB)
    Maxblocks
    Increment by
    User size(MB)
    User blocks
    /oracle/SID/sapdata1/temp_1/temp.data1
    1
    PSAPTEMP
    2,048.00
    262,144
    AVAILABLE
    1
    NO
    0
    0
    0
    2,047.00
    262,016
    /oracle/SID/sapdata1/temp_2/temp.data2
    2
    PSAPTEMP
    2,048.00
    262,144
    AVAILABLE
    2
    NO
    0
    0
    0
    2,047.00
    262,016
    /oracle/SID/sapdata1/temp_3/temp.data3
    3
    PSAPTEMP
    2,048.00
    262,144
    AVAILABLE
    3
    NO
    0
    0
    0
    2,047.00
    262,016
    /oracle/SID/sapdata3/temp_4/temp.data4
    4
    PSAPTEMP
    3,072.00
    393,216
    AVAILABLE
    4
    NO
    0
    0
    0
    3,071.00
    393,088
    /oracle/SID/sapdata2/temp_5/temp.data5
    5
    PSAPTEMP
    1,024.00
    131,072
    AVAILABLE
    5
    NO
    0
    0
    0
    1,023.00
    130,944
    /oracle/SID/sapdata2/temp_6/temp.data6
    6
    PSAPTEMP
    1,024.00
    131,072
    AVAILABLE
    6
    NO
    0
    0
    0
    1,023.00
    130,944
    Any ideas how to resolve this or is it a bug?
    Thanks
    Craig

    Hi Craig,
    Deactivating the alert could be the latest solution, but you should first check how the tempfiles are setup. If they are set as sparse files they might not use all the allocated space at FS level, but might grow up to it and cause an overflow...
    To deactivate that behavior you should copy temp files with a specific cp option (--sparse=never) to deactivate the sparse attribute as explained in the here under notes (the 2nd one is for 11g only thus not valid for you).
    Regards
    548221 - Temporary Files are created as sparse files
    Oracle creates files of temporary tablespaces as sparse files.
    'Sparse' is a special property a file in Unix operating systems can have. Sparse files are files that can dynamically grow and shrink depending on their content. So many sparse files can use a common pool of free disk space. Also the creation of a sparse file is much faster than creation of a normal file.
    Problems can occur if sparse files on the same disk grow in parallel and there is not sufficient free disk space for all to extend.
    Usage of sparse files is not a bug. Therefore there is no possibility to tell Oracle not to use sparse files for the temporary tablespace if the operating system offers sparse file functionality.
    1864212 - Forcing complete space allocation for temp files
    By default, temp files are not initialized when the file is created and therefore the disk space is not pre-allocated in the file system.

  • Calculate PSAPTEMP size before creating aggregate?

    Hi Experts,
    While i am creating aggregate job is ended with error.
    SQL Error: 12801
    I checked in SM21 and meaning of error is "Overflow of database objects " so while creating aggregate PSAPTEMP become overflow.
    My question is how much exact size it requires while creating aggregate, now we our PSAPTEMP table space size is 10 GB.
    How to calculate the required size to increase PSAPTEMP tablespace?
    Thanks &&& Regrs,
    KD.

    hi,
    PSAPTEMP is primarily used  temporarily to store results of the aggregation and final data is typically stored in a user tablespace. So if your PSAPTEMP tablespace is too small you can only increase its size.
    i think that will solve your purpose
    Also, there can be a scenario when are unable to do the same, so you need to rearrange your aggregates.
    In that case the aggregates will be activated. First the aggregates with more data  and then with less data
    generally PSAPTEMP tablespace should be at least twice as large as the largest index.
    please refer SAP Note 659946 and 600513 for more details
    regards
    laksh.

  • MVNTXCNV.ELG Error

    Hi
    We are facing the next error at the 'MVNTXCNV.ELG' phase:
    Contents of  'MVNTXCNV.ELG'
    2EETQ399 View latest 'TP*.ECO' files in log-directory for details.
    2EETQ399 Dialogue: ERROR
    2EETQ399 Log file analyse of 'tp ddlntabs' operation:
    2EETQ399 -> single errors (code <= 8) found in logfile
    2EETQ399 Errors are accumulated in file 'MVNTXCNV.ELG'
    Contents of TP00.ECO - Latest Files
    BLOCKED SIGNALS: ''
    SAPup> Starting subprocess 24672 at 20080410134527
    ENV <0x9ffffffffffff83c>: ORACLE_PSRV=SUP
    ENV <0x9ffffffffffffb7f>: NLS_LANG=AMERICAN_AMERICA.WE8DEC
    ENV <0x9ffffffffffffbac>: ORACLE_BASE=/oracle
    ENV <0x9ffffffffffffbe5>: dbs_ora_tnsname=SUP
    ENV <0x9ffffffffffffc05>: ORACLE_SID=SUP
    ENV <0x600000000019c600>: DIR_LIBRARY=/usr/sap/put/exe
    ENV <0x9ffffffffffffc7b>: ORA_NLS=/oracle/SUP/102_64/ocommon/NLS_723/admin/data
    ENV <0x600000000018e590>: dbs_ora_schema=SAPR3
    ENV <0x9ffffffffffffd30>: ORA_NLS32=/oracle/SUP/102_64/ocommon/NLS_733/admin/data
    ENV <0x9ffffffffffffd68>: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
    ENV <0x9ffffffffffffe12>: ORACLE_HOME=/oracle/SUP/102_64
    ENV <0x9ffffffffffffe4d>: dbms_type=ORA
    ENV <0x600000000019ca00>: LD_LIBRARY_PATH=/usr/sap/put/exe:/opt/java1.5/jre/lib/IA64N:/opt/java1.5/jre/lib/IA64N/server:/opt/java1.5/jre/../lib/IA64N
    ENV <0x600000000018e990>: auth_shadow_upgrade=0
    EXECUTING /usr/sap/put/exe/tp (tp) pf=/usr/sap/put/bin/XTERN_CNV.TPP ddlntabs SUP ddlmode=F step=X protyear=00 shadow_only strel=46C substext=4G -Dbuffreset=no touch=NO
    This is /usr/sap/put/exe/tp version 372.03.35 (release 700)
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    Warning: Parameter STARTDB is no longer used.
    Warning: Parameter STOPDB is no longer used.
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    supadm>
    can anyone help
    Thanks & Regards
    Senthil

    Sure Will Do that Shaji.
    Is PSAPTEMP tablespace used in oracle10g/ECC6.0? bcos in our upgraded development box, the used space is always Zero.
    So I doubt whether PSAPTEMP is used or not?
    Regards
    Senthil

  • How to move client from one server to other at remote location

    Dear All,
    We have two servers located in two different locations.Due to some network issues i am unable to do the remote client copy .
    Please suggest how do i take client 100 to other server which is at different location and on different platform.
    Source system is HP Unix Target system is on windows2003, database is oracle on both servers.
    Regards,
    Najeeb ..

    Dear Shark,
    Please check whether you have set archive logs.
    If you have set then please disable, it since it will increase size of /oracle/SID/oraarch.
    then you need to take achive backup. so all the above please ensure that no archive logs are generated.
    also check the size of PSAPUNDO and PSAPTEMP tablespace and if possible make its size large.
    Have you enabled Automated Undo managemant. if your database is oracle9 then you need to manually provide AUM or else it is automatic in higher oracle DB.
    Check the logs of Client copy using scc3.. all the best for all.
    Regards,
    Ganesh

  • DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

    Hi All,
    We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
    Runtime Error          DBIF_REPO_SQL_ERROR
    Date and Time          08.01.2008 13:01:08
         1. A printout of the problem description (short dump)
            To obtain this, select in the current display "System->List->
            Save->Local File (unconverted)".
         2. A suitable printout of the system log
            To obtain this, call the system log through transaction SM21.
            Limit the time interval to 10 minutes before and 5 minutes
            after the short dump. In the display, then select the function
            "System->List->Save->Local File (unconverted)".
         3. If the programs are your own programs or modified SAP programs,
            supply the source code.
            To do this, select the Editor function "Further Utilities->
            Upload/Download->Download".
         4. Details regarding the conditions under which the error occurred
            or which actions and input led to the error.
         Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
         Please check the entries in the system log (Transaction SM21).
         You may able to find an interim solution to the problem
         in the SAP note system. If you have access to the note system yourself,
         use the following search criteria:
         "DBIF_REPO_SQL_ERROR" C
         "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
         "CHECK_IF_ANALYZE_IS_NESSESSARY"
    System environment
        SAP Release.............. "640"
        Application server....... "psapdb"
        Network address.......... "158.58.65.11"
        Operating system......... "AIX"
        Release.................. "5.3"
        Hardware type............ "00CD615C4C00"
        Character length......... 16 Bits
        Pointer length........... 64 Bits
        Work process number...... 22
        Short dump setting....... "full"
        Database server.......... "psapdb"
        Database type............ "ORACLE"
        Database name............ "BWP"
        Database owner........... "SAPBWP"
        Character set............ "C"
        SAP kernel............... "640"
        Created on............... "Oct 29 2006 20:49:57"
        Created in............... "AIX 1 5 00538A4A4C00"
        Database version......... "OCI_920 "
        Patch level.............. "155"
        Patch text............... " "
        Supported environment....
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
         10.2.0.."
        SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16192
    EM....................... 16759424
    Heap..................... 0
    Page..................... 24576
    MM Used.................. 6604384
    MM Free.................. 1772536
    SAP Release.............. "640"
    User and Transaction
        Client.............. 200
        User................ "R3REMOTE"
        Language key........ "E"
        Transaction......... " "
        Program............. "SAPLRSSM_PROCESS"
        Screen.............. "SAPMSSY0 1000"
        Screen line......... 6
    Information on where terminated
        The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
         "CHECK_IF_ANALYZE_IS_NESSESSARY".
        The main program was "RSPROCESS ".
        The termination occurred in line 1143 of the source code of the (Include)
         program "LRSSM_PROCESSF04"
        of the source code of program "LRSSM_PROCESSF04" (when calling the editor
         11430).
        The program "SAPLRSSM_PROCESS" was started as a background job.
        Job name........ "BI_PROCESS_ODSACTIVAT"
        Job initiator... "RPRIYANKA"
        Job number...... 02010102
    Also we have a failed job here. Here is the job log.
    Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
    Date       Time     Message text
    08.01.2008 13:01:00 Job started
    08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
    08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
    08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
    08.01.2008 13:01:02 STATISTICS
    08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
    08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
    08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
    08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
    08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
    08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
    08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
    08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
    08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
    08.01.2008 13:01:08 Job cancelled
    Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
    Please help.

    The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
    Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
    So, adding more space to the filesystem solved the problem.
    Thanks to everyone who have shown interest in solving my problem.

  • An error occurred in the source system, DBIF_RSQL_SQL_ERROR

    Dear All,
    last 4 days my process chain stop, now todya i activate the process chain. i found a error In 0FI_AR-4.
    the error i found
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    i already check in RSA3 , Once execute 0FI_AR_4 I Found a dump
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "BWFIR_READ_BSID_CPUDT_DATA" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "BWFIR_READ_BSID_CPUDT_DATA"
    "(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-25153: Temporary Tablespace is Empty"
    Internal call code.........: "[RSQL/FTCH/BKPF_BSID ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "SAPLBWFIR" or "LBWFIRU10"
    "BWFIR_READ_BSID_CPUDT_DATA"
    please any one help on this issue
    Advance in thanks
    Regards
    Priya

    Hi,
    Can you please try adding the datafile to the PSAPTEMP tablespace in the source system, and try to start the process chain again. If required you have to contact the Basis Administration. Also please find the system logs and dumps in the source system at the point of time.
    Can you please let me know if it got fixed.
    Thanks & Regards,
    VR

  • Oracle 10.2.0.4 to 11.2.0.3 upgrade

    Hi All,
    I have a BI EHP2 system with Linux / Oracle 10.2.0.4 .
    We are into the upgrade process > We are getting some error during the pre_upgrade scripts.
    SQL> @pre_upgrade_tasks.sql
    ================================
    === PRE-UPGRADE Tasks: START ===
    ================================
    Date       Time                                                                
    2012-03-08 18:33:58                                                            
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    TIMESTAMP                                                                      
    COMP_TIMESTAMP UTLRP_BGN  2012-03-08 18:33:58                                  
    PL/SQL procedure successfully completed.
    TIMESTAMP                                                                      
    COMP_TIMESTAMP UTLRP_END  2012-03-08 18:34:15                                  
    PL/SQL procedure successfully completed.
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
    OBJECTS WITH ERRORS                                                            
    7                                                            
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
    ERRORS DURING RECOMPILATION                                                    
    1                                                    
    PL/SQL procedure successfully completed.
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    SQL> PURGE DBA_RECYCLEBIN;
    DBA Recyclebin purged.
    SQL> SET ECHO OFF
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    SQL> EXECUTE dbms_stats.gather_dictionary_stats;
    PL/SQL procedure successfully completed.
    SQL> SET ECHO OFF
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 03-08-2012 18:37:32                              
    Script Version: 11.2.0.3.0 Build: 001                                                              
    Database:                                                                               
    --> name:          CD1                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Linux x86 64-bit                                                                
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 966 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 400 MB                                                                 
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 377 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 60 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  INVALID                                                
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 14.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    WARNING: --> Database contains INVALID objects prior to upgrade.                                   
    .... The list of invalid SYS/SYSTEM objects was written to                                         
    .... registry$sys_inv_objs.                                                                        
    .... The list of non-SYS/SYSTEM objects was written to                                             
    .... registry$nonsys_inv_objs.                                                                     
    .... Use utluiobj.sql after the upgrade to identify any new invalid                                
    .... objects due to the upgrade.                                                                   
    .... USER SYS has 8 INVALID objects.                                                               
    ===================================
    === PRE-UPGRADE Tasks: FINISHED ===
    ===================================
    SQL> spool off
    There are 2 errors
    1.)Object with errors or invalid objects
    2.) recompilation error
    1.) Object with errors or invalid objects
    These are 7 object
    AQ$_KUPC$DATAPUMP_QUETAB_V
    KUPC$DATAPUMP_QUETAB
    SYSNTuqbWKWtJPc7gQMEKFx9cXA==
    SYSNTuqbWKWtLPc7gQMEKFx9cXA==
    SYSNTuqbWKWtNPc7gQMEKFx9cXA==
    AQ$_KUPC$DATAPUMP_QUETAB_F
    AQ$_KUPC$DATAPUMP_QUETAB
    2.)recompilation error
    We queried the UTL_RECOMP_ERRORS table and found
    156977
    09-MAR-12 10.08.35.
    ORA-01403: no data found
    ORA-01403: no data found.
    Please suggest how to proceed.
    Br
    Anthony

    Hello Anthony,
    even maybe not on Windows (I faced this on Unix), proceed with invalid objects as in : Note 1453935 - Invalid DataPump objects after Windows patch collection > 25
    this is the leftover of some previous 10g patching. Once objects are recreated, recompilation will go ok.
    Regards,
    Igor

  • Oracle Upgrade --  Pre-Upgrade 10.2.0.4 to 11.2.0.1

    Hello,
    I want to do an Oracle Upgrade to version 11.2g!
    At this point I did some things (in Windows Server 2003 X64):
    1-) Install Oracle 10.2.0.1 (DVD Media);
    2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
    3-) Installation of interim / last generics patch (note 1137346);
    4-) Installation of SAP ECC 6.0 SR3 by SAPInst
    5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
    As you see above, all the SAP system was well installed!
    But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
    So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
    I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
    Next I will post here this two log scripts... they are long!!!

    PRE_UPGRADE_TASKS.log:
    SQL> @pre_upgrade_tasks.sql
    PRE-UPGRADE Tasks: === START ===
    2010-08-05 18:24:13                                                                               
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
    DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
    DOC>   objects in the database. Recompilation time is proportional to the
    DOC>   number of invalid objects in the database, so this command may take
    DOC>   a long time to execute on a database with a large number of invalid
    DOC>   objects.
    DOC>
    DOC>   Use the following queries to track recompilation progress:
    DOC>
    DOC>   1. Query returning the number of invalid objects remaining. This
    DOC>       number should decrease with time.
    DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    DOC>
    DOC>   2. Query returning the number of objects compiled so far. This number
    DOC>       should increase with time.
    DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
    DOC>
    DOC>   This script automatically chooses serial or parallel recompilation
    DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
    DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
    DOC>   On RAC, this number is added across all RAC nodes.
    DOC>
    DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
    DOC>   recompilation. Jobs are created without instance affinity so that they
    DOC>   can migrate across RAC nodes. Use the following queries to verify
    DOC>   whether UTL_RECOMP jobs are being created and run correctly:
    DOC>
    DOC>   1. Query showing jobs created by UTL_RECOMP
    DOC>          SELECT job_name FROM dba_scheduler_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>
    DOC>   2. Query showing UTL_RECOMP jobs that are running
    DOC>          SELECT job_name FROM dba_scheduler_running_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>#
    COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
                      0                                                                               
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
                              0                                                                        
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    Truncating SYS.AUD$
    This reduces the time needed for upgrading the database.
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
    Script Version: 11.2.0.1.0 Build: 003                                                              
    Database:                                                                               
    --> name:          PRD                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Microsoft Windows x86 64-bit                                                    
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 905 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 84 MB                                                                  
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 210 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 61 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  VALID                                                  
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 11.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    Recommendations                                                                               
    Oracle recommends gathering dictionary statistics prior to                                         
    upgrading the database.                                                                            
    To gather dictionary statistics execute the following command                                      
    while connected as SYSDBA:                                                                               
    EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
    Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
    To view existing hidden parameters execute the following command                                   
    while connected AS SYSDBA:                                                                               
    SELECT name,description from SYS.V$PARAMETER WHERE name                                        
            LIKE '\_%' ESCAPE '\'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    Oracle recommends reviewing any defined events prior to upgrading.                                                                               
    To view existing non-default events execute the following commands                                 
    while connected AS SYSDBA:                                                                         
      Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
          WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
    Trace Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
          WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    PRE-UPGRADE Tasks: === FINISHED ===
    SQL> spool off

  • Error at "spacechk_ini" phase with SQL ERROR 942: ORA-00942

    Dear support,
    I am posting this problem again in upgrade forum as i am still dont have proper answer.
    We are performing upgrade from 4.0B (4.0B Ext kernel level 996 , windows 2000 Oracle 9.2.0.5  ) to 4.7 Ext 2.00 SR1. I have upgraded my database from 8.1.7.4 to 9.2.0.5 as prerequisite for upgrade.
    While performing Initialization module we got below error
    " No DB freespace check possible code -4 "
    When i analyzed slog found below error
    Phase SPACECHK_INI:
    ERROR: Statement: SELECT "TABLESPACE_NAME", "BYTES"/1048576 FROM SYS."DBA_TEMP_FILES" WHERE "BYTES" >= 1048576
    ERROR: SQL ERROR 942: ORA-00942: table or view does not exist
    ERROR: Statement: SELECT "TABLESPACE_NAME", "BYTES"/1048576 FROM SYS."DBA_TEMP_FILES" WHERE "BYTES" >= 1048576
    ERROR: ERROR 256: invalid cursors id
    ERROR: SQL ERROR 942: ORA-00942: table or view does not exist
    have observed one more thing at my database ( which is now upgraded to 9.2.0.5 as prerequisite for upgrade to 4.7)
    select * from dba_temp_files;
    no rows selected.
    But when i run same querry to my another server which is 4.7 oracle 9.2.0.5 i get output as list of datafiles with PSAPTEMP tablespace.
    I think problem might be this fixed tables/view dba_temp_files is showing no rows as PSAPTEMP tablespace.Also we cannot add any value to this table as it is fixed tabel/view.
    How we can troubleshoot this?
    I would also like to inform in my 40 B database PSAPTEMP tablespace is dictionary managed after upgrade to 9.2.0.5 but
    In another server which is 4.7 9.2.0.5 , PSAPTEMP tablespace is locally managed
    May be this is the problem why my dba_temp_files showing nothing.
    Do i need to perform DMTS to LMTS for psaptemp tablespace.so that my dba_temp_files view will show me psaptemp tablespace under it?
    Can anybody suggess something on the same at earliest ?
    Best Regards,
    AjitR

    Markus ,
    Thanks for reply but i have performed database refresh of my DEV server long time back. Now as part of upgrade i have also performed Oracle upgrade from 8.1.7.4 to 9.2.0.6 . Now how can i bring data in dba_temp_files.
    Shouls i go for drop and recreate PSAPTEMP tablespace option.
    Please guide me in detail as i cannot restore backup from any other server to DEV because database already upgraded.
    Best Regards,
    AjitR

  • Client Copy  canceled

    Hi Guys,
    I scheduled a client copy job. A few minuites after the job started from SCC3 it shows client copy canceled. SM21, System Log displayed the following message:
    Database error 25153 at EXE
    I need to run the client copy.
    Please, what can I do to resolve this problem?
    Cheers,
    Daniel

    Hi Daniel,
    Please check your PSAPTEMP tablespace status. Open BRTOOLS from SIDADM login or ORASID login and go by options.
    It will show you tablespace status. If you find its running out of space please add some space into it and re-execute the client copy.
    BRTOOLS --> 2.Space management --> then "continue" and it will give you option as "Show Tablespace".
    Hope this clarifies. Should you have any more query, please let us know in the forum.
    <removed_by_moderator>
    Read the "Rules of Engagement"
    Regards,
    Sujit.
    Edited by: Juan Reyes on Mar 7, 2011 9:16 AM

  • Unable to extend temp segment by 128 in tablespace PSAPTEMP

    Hi everybody!
    While processing a UNICODE coversion with SAPINST on my SAP NW2004s system (AIX 5,2  - Oracle 10.2 - BW 7.0) into my.SAPDFACT_1.log file the following errors occured:
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "HBQ20080503070541                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "si088ss1                                                        "
    (GSI) INFO: sysname  = "AIX"
    (GSI) INFO: nodename = "si088ss1"
    (GSI) INFO: release  = "2"
    (GSI) INFO: version  = "5"
    (GSI) INFO: machine  = "0031832B4C00"
    (DB) INFO: /BIC/FZHPY_LIM created #20080503200234
    (IMP) INFO: import of /BIC/FZHPY_LIM completed (133182692 rows) #20080503212420
    DbSl Trace: Error 1652 in exec_immediate() from oci_execute_stmt(), orpc=0
    DbSl Trace: ORA-1652 occurred when executing SQL stmt (parse error offset=42)
    (DB) ERROR: DDL statement failed
    (CREATE UNIQUE INDEX "/BIC/FZHPY_LIM~0" ON "/BIC/FZHPY_LIM" ( "KEY_ZHPY_LIMP", "KEY_ZHPY_LIMT", "KEY_ZHPY_LIMU", "KEY_ZHPY_LIM2", "KEY_ZHPY_LIM3", "KEY_ZHPY_LIM4", "KEY_ZH
    PY_LIM5", "KEY_ZHPY_LIM6", "KEY_ZHPY_LIM7" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
    DbSlExecute: rc = 99
      (SQL error 1652)
      error message returned by DbSl:
    ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
    (DB) INFO: disconnected from DB
    Anybody can help me?
    Thanks a lot!

    Hi Stefan!
    desc SAPSR3."/BIC/FZHPY_LIM";
    Name                                      Null?    Type
    KEY_ZHPY_LIMP                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIMT                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIMU                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM2                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM3                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM4                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM5                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM6                             NOT NULL NUMBER(10)
    KEY_ZHPY_LIM7                             NOT NULL NUMBER(10)
    /BIC/ZHCONTING                            NOT NULL NUMBER(17,2)
    /BIC/ZHD_IMP                              NOT NULL NUMBER(17,2)
    /BIC/ZHPERC2                              NOT NULL NUMBER(10)
    SELECT AVG_ROW_LEN FROM ALL_TABLES WHERE TABLE_NAME = '/BIC/FZHPY_LIM';
    AVG_ROW_LEN
    SELECT BYTES, BLOCKS FROM DBA_SEGMENTS WHERE SEGMENT_NAME = '/BIC/FZHPY_LIM';
         BYTES     BLOCKS
    7180648448     876544
    SELECT FILE_NAME, TABLESPACE_NAME, BYTES, BLOCKS, AUTOEXTENSIBLE, MAXBYTES, MAXBLOCKS FROM DBA_TEMP_FILES;
    FILE_NAME
    TABLESPACE_NAME                     BYTES     BLOCKS AUT   MAXBYTES  MAXBLOCKS
    /oracle/HBQ/sapdata1/temp_1/temp.data1
    PSAPTEMP                       1048576000     128000 YES 1.0486E+10    1280000
    /oracle/HBQ/sapdata1/temp_1/temp2.data1
    PSAPTEMP                        298844160      36480 YES 3.4359E+10    4194176
    Thanks.

  • How to extend ECC6 tablespace? database is MSSQL

    Hello all,
    I intall ECC6 IDES, now I want to extend tablespace, but I didn't found command about brtools and sapdba, because my database is not oracle . how to do it? thank you.
    OS: WIndows 2003
    SAP release: ECC 6
    database: Microsoft MSSQL 2005

    (SQL Server Management Studio)
    SQL Server 2005
    SQL Server 2008 R2
    SQL Server 2008
    SQL Server 2012
    This topic describes how to increase the size of a database by using Object Explorer in SQL Server Management Studio. The database is expanded by either increasing the size of an existing data or log file or by adding a new file to the database.
    To increase the size of a database
    In Object Explorer, connect to an instance of the SQL Server 2005 Database Engine, and then expand that instance.
    Expand Databases, right-click the database to increase, and then click Properties.
    In Database Properties, select the Files page.
    To increase the size of an existing file, increase the value in the Initial Size (MB) column for the file. You must increase the size of the database by at least 1 megabyte.
    To increase the size of the database by adding a new file, click Add and then enter the values for the new file
    Click OK.
     

Maybe you are looking for