Skip to Content

Data is missing

Hi all,

I made copy of SAP Datafile from PRD to New TEST server and archives successfully applied on New server and alter database opened successfully with resetlogs.

the MM,QM,PP,PM, CS's data is getting match on both server but FI and SD users are executing their reports

with same selection criteria they are saying that SD and FI data is not getting match of current PRD with New server.

when i checked entries of BS* Table(BSAD,BSAK,BSAS,BSID,BSIP,BSIS) with same date on current and new PRD then

they are not same while table entries matched of big tables like MSEG, BSEG, MKPF etc..

would you tell, why I am getting this issue in SD module while database successfully opened.

how can I sort out this issue?

Regards

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Feb 20, 2012 at 09:27 AM

    Hi,

    It seems that you have not applied latest archive redo logs files and opened the database .This is resulting in missing data from the database.

    You should check the data only upto date and time upto which you have applied the redo log files.In such a case you may find matching data in TEST and PRD.

    Regards,

    Deepak Kori

    Add comment
    10|10000 characters needed characters exceeded

    • hi respected Deepak,

      thanks for your reply,

      Dear, I just ran the SGEN, update the stats with DB13 and brtools, refreshed DB via DB02 and there are not showing any missing index.

      now I am going to run following commands

      SQL>catupgrd.sql and utlrp.sql

      DOC>   Next shutdown immediate, restart for normal operation, and then
      DOC>   run utlrp.sql to recompile any invalid application objects.
      DOC>
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>#
      SQL> shutdown immediate
      Database closed.
      Database dismounted.
      ORACLE instance shut down.
      SQL> startup
      ORACLE instance started.
      
      Total System Global Area 1.0402E+10 bytes
      Fixed Size                  2094736 bytes
      Variable Size             721422704 bytes
      Database Buffers         9663676416 bytes
      Redo Buffers               14680064 bytes
      Database mounted.
      Database opened.
      SQL> @E:\oracle\PRD\102\RDBMS\ADMIN\utlrp.sql
      
      TIMESTAMP
      --------------------------------------------------------------------------------
      
      COMP_TIMESTAMP UTLRP_BGN  2012-02-21 22:59:09
      
      1 row selected.
      
      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>#
      
      PL/SQL procedure successfully completed.
      
      
      TIMESTAMP
      --------------------------------------------------------------------------------
      
      COMP_TIMESTAMP UTLRP_END  2012-02-21 22:59:13
      
      1 row selected.
      
      
      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
      -------------------
                        0
      
      1 row selected.
      
      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
      ---------------------------
                                0
      
      1 row selected.
      
      
      PL/SQL procedure successfully completed.
      

      Regards,