ITPub博客

首页 > 数据库 > Oracle > Oracle General Ledger Troubleshooting Guide For Open/Close Period

Oracle General Ledger Troubleshooting Guide For Open/Close Period

原创 Oracle 作者:moonsoft 时间:2019-07-13 07:36:04 0 删除 编辑
Troubleshooting Guide for Open Period[@more@]
Doc ID: 135909.1Type: TROUBLESHOOTING
Modified Date : 15-APR-2009Status: PUBLISHED

Checked for relevance on 15-Apr-09


PURPOSE
-------

This guide is meant to help you debug and gather information needed for 
analyzing Open Period problems that occur in Oracle General Ledger.

 
SCOPE & APPLICATION
-------------------

This guide is designed for technical and functional users.


Oracle General Ledger 
---------------------
Troubleshooting Guide for Open Period
-------------------------------------
August 2006 (reviewed April 2009)


The following guidelines will help you with troubleshooting Open Period. 


Step 1.  Is this a new install of Oracle General Ledger?  Are you trying
         to open the first period ever in this set of books?

Step 2.  Are you trying to open the first period of a new fiscal year?

Step 3.  What Period Type is used for your set of books? How many periods
         per year should that Period Type have? Have you defined that many
         periods, of that type, for the current/next fiscal year? 

Step 4.  Are you on the latest version of the GLOOAP code?

         To find the version of an executable, at the operating system level, 
         go to your GL_TOP directory and grep for the header file in the 
         executable.

         Unix:
 
         Cd $GL_TOP/bin

         Strings -a GLOOAP|grep '.opc'

         NT:
         find /i ".opc" GLOOAP

Step 4.  Do you have your logfile?   

         It is important to have the most recent concurrent process logfile 
         in front of you.  

Step 5.  What makes you think that you are having a problem?

         Is there an error on the Open Period log?
 
         Does the Open/Close Period form show results you are not expecting?

Step 6.  If there is an 'ORA' error on the log file, have you showed it to
         your DBA? 

         In most cases, ORA errors are database level errors that need to be 
         resolved by your DBA. 

Step 7.  If you have Oracle Diagnostics installed, run the Period Close test.
         Review this for errors.


Note: Storage parameters for General Ledger temporary and interim tables,
      and indexes must be entered on the Storage Parameters form in General 
      Ledger (navigation = Setup..System..Storage). 



Some Common Open Period Errors
------------------------------

1.  APP-00969 Program was terminated by Signal 4.

Retained Earnings accounts for all balancing segment values must be
enabled. If not existing already, and dynamic insertion is enabled, there
must not be any security or cross validation rules that will prevent 
their creation. If dynamic insertion is not enabled, you must pre-create
the accounts.
For further information, see
Note 1037958.6 
Note 1041466.6 
 

2.  USD-SPN:  Process exited with status 268435468 (on VMS)

See the solution for error 1 above.


3.  Please choose an existing combination.
    The following combination is erroneous and does not exist:
    638-000-000-299100-000-000-00000
    SHRD0015: fdfkfa-FFSEGSID failed:
    > Ret CCIDwhich failed validation, 
       does not exist...
    > Error returned bygloire...
    SHRD0026: Current system time is: 02-JAN-200109:55:13
    *****************************************************
    sqlcaid:sqlabc: 0  sqlcode: 1403  sqlerrml: 25
    sqlerrmc:
    ORA-01403: no datafound
    sqlerrp:        sqlerrd: 0 0 0 0 0 538976288
    sqlwarn:    sqltext:
    *****************************************************

See the solution for error 1 above. In this case, you are given the combination
that must be created/enabled: 638-000-000-299100-000-000-00000


4.  ORA-01654: Unable to extend index GL.GL_BALANCES_N1 by 999 in
    tablespace GLX

Cause:  Failed to allocate extent for index segment in tablespace.
Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more 
        files to the specified tablespace.

See Note 1025288.6 for more information.


5.  ORA-01653: Unable to extend table GL.GL_POSTING_INTERIM by 999 in
    tablespace GLD

Cause:  Failed to allocate an extent for table segment in tablespace. 
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more 
        files to the tablespace indicated.

You must update the storage parameters for this interim table on the
Storage Parameters form in General Ledger.


6.  ORA-01632: max # extents reached in index GL.GL_POSTING_INTERIM_N1

Cause:  The named index has reached its MAXEXTENTS setting
Action: If possible, increase the value of either the MAXEXTENTS 
        storage parameter or recreate the index with a larger
        extent size.

You must update the storage parameters for this interim index on the
Storage Parameters form in General Ledger.


7.  ORA-01632: max # extents reached in index GL.GL_BALANCES_N3

Cause:  The named index has reached its MAXEXTENTS setting
Action: If possible, increase the value of either the MAXEXTENTS 
        storage parameter or recreate the index with a larger
        extent size.


8.  OOAP0010: Please define calendar periods before opening them.

You must verify that the calendar is correctly defined for the current 
fiscal year. You have specified a Period Type for the set of books.
The Period Type is defined to have a fixed number of periods. You must
have that number of periods, of that period type, defined for your 
fiscal year.  

For example: If the period type is defined as having 13 periods, 
             then there must be 13 periods defined in your calendar, 
             with that period type. 
             If you find only 12 periods, create the 13th, then 
             try to open the period again.


9.  ORA-01562: failed to extend rollback segment number 3.

This is normally followed by another error message that caused
the failure. Shutdown, restart and then take appropriate action for
the error the caused the failure. If starting up the system
again doesn't solve the problem, it is possible that there is
an active transaction in the rollback segment and the system
can't roll it back for some reason. Check the trace file
generated by the PMON process for more information.

For more information see the following:

Note 10579.1 Subject:  How many Rollback Segments to Have
Note 69464.1 Rollback Segment Configuration and Tips
Note 62005.1 Creating, Optimizing and Understanding Rollback Segments
Note 107085.1 Tuning Rollback Segments

Also, for the Open Period program, you can specify a rollback segment
to be used whenever the program runs. Open Period typically requires a
rollback segment larger than that used for normal transaction processing.
The Concurrent Program Controls window allows you to assign the large
rollback segment once during your setup process.



Search Words
------------
gl_posting_interim_n

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/226700/viewspace-1024863/,如需转载,请注明出处,否则将追究法律责任。

上一篇: 上线后2-4维护
请登录后发表评论 登录
全部评论

注册时间:2005-01-20

  • 博文量
    412
  • 访问量
    319373