Resource Constraint

hi,
We are working with resources in which many products can be scheduled based on sizes. Hence, we use size as a characteristic for resource and product. But while defining the characteristic value for resource it will be Resource A: Size:25-75mm, B: Size: 75-125mm.
If I get a product for 78 dia, System should automatically schedule in resource B.   Is it possible? In case of nay solution please help.
Thanks in advance
dhaiva

Hi
You will need alternate resources setting on your PDS (or PPM) selectable by characteristic. To see how this is configured look at the building block S16 - Production Planning for the configuration, Section 2.1.7 Maintaining Alternate Resources:
[Production Planning - Best Practice Configuration Guide|http://help.sap.com/bp_scmv250/BBLibrary/Documentation/S16_BB_ConfigGuide_EN_DE.doc]
Regards
Ian

Similar Messages

  • Production planning with resource constraint in APO

    Hi All,
    Could you please share some documents on  " Production planning with resource constraint in APO" or
    If possible,kindly  proivde some business scenario with the above concept and and its sequence steps.
    Regards
    Vel

    Hi Velavan,
    You may refer to the related links below on SAP Library, please navigate further in the menu which appear in these links to get details on sub-topics.
    http://help.sap.com/saphelp_ewm70/helpdata/en/a5/8b623c8a6da167e10000000a11402f/content.htm
    https://help.sap.com/saphelp_scm70/helpdata/en/4c/6af71b832821d1e10000000a42189c/frameset.htmHi
    You may also refer to the standard SAP PPDS book SCM 250 for more information.
    Regards,
    Umesh

  • Resource details are not getting displayed in gantt chart -- R12 instance

    Hi All,
    we are working on a scenarior in R12 instance.
    when we run a resource constraint plan and navigate to Gantt chart the complete application is getting hanged and it is not Displaying any resource details.
    Before 2 days we were able to view the Gantt chart and resource details were populating properly.
    Resource Avalability and usage is correct.
    Thanks,
    Vasudha

    Hi
    In R12 Gantt chart is enhanced to show resource gantt in 3 different view. Res units view,resource hours view and res availability view.
    Please do the following and see if it works.
    On work bench go to Tools , preferences > set gantt chart preferences. even if u want to leave them as default, uncheck something save., and check again and save.
    Let me know if it works.
    Tnx
    Partha

  • Project Templates with Enterprise Resources

    I'm using Project Server 2013 ( latets updates installed for both Client and Server)
    I've created a project template and attached this to a project type. My template has enterprise resources speciified. So far so good.
    Now I'm trying to create a project using this template and I'm getting some errors.  (See below)
    As soon as I remove the resources from my template the project creates fine.
    It looks like 'rsResourceCannotAddLocalWithSameNameAsEnterprise'  in the error below means that Project Server looks at the resource in the template and considers the resources in the template always to be a local resources. And of
    course the resource already exists in my enterprise resources and therefore the project creation fails.
    Datasets:
    ProjectDataSet
    Table ProjectResource
    Row:  RES_UID='0bb2c5b5-1716-e311-a1c1-005056992257' PROJ_UID='3121855b-f13b-e311-9f7f-005056991b52'
    Error rsResourceCannotAddLocalWithSameNameAsEnterprise (2058) - column
    RES_UID
    General
    Queue:
    GeneralQueueJobFailed (26000) - ProjectCreate.ProjectAddToMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='353d845c-f13b-e311-9f7f-005056991b52' JobUID='3a21855b-f13b-e311-9f7f-005056991b52' ComputerName='13fdabbe-0ac0-4cca-b382-49d1853aec73'
    GroupType='ProjectCreate' MessageType='ProjectAddToMessage' MessageId='1' Stage='' CorrelationUID='147f4f9c-ae30-b04b-aec7-382a52fa5fdf'. For more details, check the ULS logs on machine
    13fdabbe-0ac0-4cca-b382-49d1853aec73 for entries with JobUID
    3a21855b-f13b-e311-9f7f-005056991b52.
    My questions are:
    Are Enterprise Resources in templates supported?
    Is there a way around this? We're trying to make it easy to select a subset of the enterprise resources available.

    I have experienced this exact same thing and my situation is highly irregular. 
    This is with Project Server 2013.
    I had an EPT with a Project Schedule that had Generic Enterprise Resources assigned and was able to create new projects without problems using the EPT from the New button in the Project Centre in PWA.
    I was creating new projects to test and demonstrate Portfolio Analysis and was able to model Organisational Capacity represented by my Generic Resources and also the Surplus/Deficit element of Resource Constraints on a Portfolio. The Hired Resource Report
    was failing.
    A Service Pack and Cumulative update were applied to the Server and now I cannot create new projects using EPTs that have a project schedule with Generic Enterprise Resources assigned to tasks in the schedule.
    I checked the error message for the Failed and Blocking job in the queue and the GUIDs were for my Generic Enterprise Resources. I deleted the offending Generic Enterprise Resources and then re-created them anew, edited the Project Template to have
    these Generic Enterprise Resources on the Project Team and randomly assigned them to tasks in the schedule to generate a notional demand for work in the Project Template. I then Saved the Template in Project as a new Project Template and edited my EPT
    to reference this new Project Schedule. 
    Same error encountered again.
    Perversely I can open the Template schedule in Project Professional and do Save As and save it as a new project to the Server and that works just fine - the schedule is visible in the Project Centre and I can edit the schedule in both Project Pro and in
    PWA.
    My hunch is that the Cumulative Update and Service Pack which were applied to try and resolve the failing "Hired Resources Report" in Portfolio Analysis, which sadly it didn't resolve - has probably provoked this interesting challenge as it is
    the only material thing to change on the Server during the time that this issue has manifested itself.
    Am I the only one to encounter this?
    Dominic Moss | MAPM Microsoft Certified Technology Specialist | Our Newsletter:
    PM News Project Server Specialists
    Project Server PRIME | Twitter:
    @Twitter | Facebook:
    @Facebook | Linkedin:
    Wellingtone

  • WIP RESOURCE TRANSACTION에러

    제품 : MFG_WIP
    작성날짜 : 2005-05-30
    WIP RESOURCE TRANSACTION에러 "USER NAME NOT VALID. PLEASE RE-ENTER"
    =================================================================
    PURPOSE
    "User name not valid. Please re-enter" Error를 가진 Pending Resource
    Transaction에 대한 해결방법
    Problem Description
    a) Resource Transaction이 Pending됨
    Error Message: "User name not valid. Please re-enter"
    b) Navigate to > Resource transaction > Resource transaction Resources
    charge type = 'Manual'인 Resource에서 발생함.
    c) Component들은 Lot/Serial Controll Item임.
    Workaround
    N/A
    Solution Description
    원인 > 이 문제는 Resource에 대해 manual하게 Charge된 경우에
    발생한다.
    Fix방법>
    a) Increase the file version of WIPTXRSC.fmb to 115.51.1159.2
    b) Apply patch 3532800 or higher
    Reference Documents
    Note:292661.1

    If you manually create discrete jobs the system does not normally check constraints. The standard planning engine is infinite capacity. If you want to check for resource constraints during planning (finite capacity) you need to use Advanced Planning and Sceduling.

  • Guide Line for zone resources control

    Hi,
    i'm looking for guide line or best practices about zone resource control, especially cpu-shares, swap and RAM.
    I need this information to make decision when customers has no idea but has a lot of zone configured.
    For example:
    t2000, 32gb ram, 32gb swap and 20 zones
    Applications run only in zones.
    How can I set cpu-shares, max-swap and capped memory just for security purpose?
    Thanks

    I'm of the opinion that the safest strategy for proactive resource management is CPU only. Playing with memory can have some effects that I'm not crazy about. Nothing unmanageable, but it can really confuse end-users unless you spend a lot of time educating them. The other consideration is that behind most resource pulls are increases in CPU use. Not always, but a lot of the time. So, if you must be proactive, go with CPU.
    The best practice will depend heavily on your environment. Do you migrate zone containers in and out of the box often? Are the apps very similar or wildly differing? Many things need to be decided before mapping out a strategy. Let's take a simple case: Fairly similar apps that don't move in and out often. Figure out what percentage of the box you want each to have, then set up dynamic resource pools to match this model.
    If you have a lot of zones and some degree of change, dynamic pools can get unwieldy, so you may prefer using the Fair share scehduler (FSS). In many cases however, proactive use of SRM means that you need to rebalance resources when you add/remove a zone.
    I think once you understand the various resource controls available to you it's best to just make a bunch of scribbles on a white board to depict what you want at a high level and then map it into a resource constraint that best implements it. The hard part is defining what you want.

  • Lock Timeouts and Heap Space Exhaustion

    I'm having some trouble figuring out the best way to handle resource constraints in my application. Generally speaking, the application works well after starting for about a day or so, but inevitably starts generating "Lock timeout" messages and eventually runs out of heap space.
    Here is the main entity class:
    http://github.com/justindthomas/flower_as/blob/master/src/java/name/justinthomas/flower/analysis/statistics/StatisticalInterval.java
    Here is a supporting, persistent class:
    http://github.com/justindthomas/flower_as/blob/master/src/java/name/justinthomas/flower/analysis/statistics/StatisticalFlow.java
    This is the data accessor:
    http://github.com/justindthomas/flower_as/blob/master/src/java/name/justinthomas/flower/analysis/statistics/StatisticsAccessor.java
    And here is the class that controls the insertion and retrieval of data:
    http://github.com/justindthomas/flower_as/blob/master/src/java/name/justinthomas/flower/analysis/statistics/StatisticsManager.java
    The general flow is that a netflow packet is received from a sensor and the StatisticsManager normalizes the flow as it is inserted into the database. The normalization converts the summarized flow into several "resolutions." For example, one resolution might be 5000 ms. So the StatisticsManager takes the flow's end time/5000 - start time/5000 and divides the volume by the result and inserts that data into the database. It sounds kind of confusing, but results in a dataset that allows me to query for netflow activity for any time frame.
    It also means that the database is queried as it is written to; existing data is updated more frequently than new data is written.
    Regardless, Sleepycat seems to be holding on to more data than it needs to. Once an interval has passed (maybe 5 minutes or so), it is unlikely to be accessed again until queried to create charts. However, the memory usage grows out of control despite the lack of necessity for keeping all but recently entered entries in cache.
    This is how the trouble generally starts (note that I've increased the timeout to 15000 ms to try to accommodate for longer wait times, but that just seems to delay the onset of the issue by a day or so):
    [#|2010-10-23T13:46:00.854-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=64;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 30264205 -1_pool-6-thread-8_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:32426808 node=17057517 type=READ grant=WAIT_NEW timeoutMillis=15000 startTime=1287866745448 endTime=1287866760795
    Owners: [<LockInfo locker="29616818 -1_pool-6-thread-5_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="7246740 -1_pool-6-thread-6_ThreadLocker" type="READ"/>, <LockInfo locker="26940477 -1_pool-6-thread-2_ThreadLocker" type="WRITE"/>, <LockInfo locker="5099094 -1_pool-6-thread-4_ThreadLocker" type="READ"/>]
    |#]
    [#|2010-10-23T15:00:41.343-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=65;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 14184769 -1_pool-6-thread-1_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:32730917 node=17057517 type=READ grant=WAIT_NEW timeoutMillis=15000 startTime=1287871223679 endTime=1287871241341
    Owners: [<LockInfo locker="23975039 -1_pool-6-thread-8_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="19650664 -1_pool-6-thread-6_ThreadLocker" type="READ"/>]
    |#]
    [#|2010-10-23T15:32:13.090-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=66;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 17937364 -1_pool-6-thread-7_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:20265315 node=17057517 type=WRITE grant=WAIT_NEW timeoutMillis=15000 startTime=1287873113904 endTime=1287873133089
    Owners: [<LockInfo locker="3251671 -1_pool-6-thread-1_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="32174859 -1_pool-6-thread-8_ThreadLocker" type="READ"/>, <LockInfo locker="33186148 -1_pool-6-thread-4_ThreadLocker" type="WRITE"/>, <LockInfo locker="17825718 -1_pool-6-thread-2_ThreadLocker" type="READ"/>]
    |#]
    [#|2010-10-23T15:32:13.096-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=64;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 32174859 -1_pool-6-thread-8_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:20265315 node=17057517 type=READ grant=WAIT_NEW timeoutMillis=15000 startTime=1287873118064 endTime=1287873133092
    Owners: [<LockInfo locker="3251671 -1_pool-6-thread-1_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="33186148 -1_pool-6-thread-4_ThreadLocker" type="WRITE"/>, <LockInfo locker="17825718 -1_pool-6-thread-2_ThreadLocker" type="READ"/>]
    |#]
    [#|2010-10-23T15:32:13.367-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=67;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 33186148 -1_pool-6-thread-4_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:20265315 node=17057517 type=WRITE grant=WAIT_NEW timeoutMillis=15000 startTime=1287873118366 endTime=1287873133366
    Owners: [<LockInfo locker="3251671 -1_pool-6-thread-1_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="17825718 -1_pool-6-thread-2_ThreadLocker" type="READ"/>, <LockInfo locker="25145711 -1_pool-6-thread-6_ThreadLocker" type="READ"/>, <LockInfo locker="5544029 -1_pool-6-thread-5_ThreadLocker" type="READ"/>]
    |#]
    [#|2010-10-23T15:33:14.030-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=68;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 31602565 -1_pool-6-thread-5_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:11219992 node=17057517 type=WRITE grant=WAIT_NEW timeoutMillis=15000 startTime=1287873175916 endTime=1287873194019
    Owners: [<LockInfo locker="27649147 -1_pool-6-thread-2_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="3895581 -1_pool-6-thread-7_ThreadLocker" type="WRITE"/>, <LockInfo locker="8345933 -1_pool-6-thread-8_ThreadLocker" type="WRITE"/>, <LockInfo locker="12576013 -1_pool-6-thread-6_ThreadLocker" type="WRITE"/>, <LockInfo locker="5695501 -1_pool-6-thread-1_ThreadLocker" type="WRITE"/>]
    |#]
    [#|2010-10-23T15:33:23.334-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=64;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 8345933 -1_pool-6-thread-8_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:11219992 node=17057517 type=WRITE grant=WAIT_NEW timeoutMillis=15000 startTime=1287873184851 endTime=1287873203333
    Owners: [<LockInfo locker="3895581 -1_pool-6-thread-7_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="12576013 -1_pool-6-thread-6_ThreadLocker" type="WRITE"/>, <LockInfo locker="5695501 -1_pool-6-thread-1_ThreadLocker" type="WRITE"/>, <LockInfo locker="13327115 -1_pool-6-thread-4_ThreadLocker" type="READ"/>, <LockInfo locker="11939897 -1_pool-6-thread-5_ThreadLocker" type="READ"/>]
    |#]
    [#|2010-10-23T15:33:23.344-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=69;_ThreadName=Thread-1;|addStatisticalSeconds Failed: (JE 4.0.104) Lock expired. Locker 12576013 -1_pool-6-thread-6_ThreadLocker: waited for lock on database=persist#Statistics#name.justinthomas.flower.analysis.statistics.StatisticalInterval LockAddr:11219992 node=17057517 type=WRITE grant=WAIT_NEW timeoutMillis=15000 startTime=1287873184893 endTime=1287873203343
    Owners: [<LockInfo locker="3895581 -1_pool-6-thread-7_ThreadLocker" type="WRITE"/>]
    Waiters: [<LockInfo locker="5695501 -1_pool-6-thread-1_ThreadLocker" type="WRITE"/>, <LockInfo locker="13327115 -1_pool-6-thread-4_ThreadLocker" type="READ"/>, <LockInfo locker="11939897 -1_pool-6-thread-5_ThreadLocker" type="READ"/>]
    |#]
    Those errors go on and on and on, until I eventually see this:
    [#|2010-10-23T17:37:29.876-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=71;_ThreadName=Thread-1;|Exception in thread "ContainerBackgroundProcessor[StandardEngine[com.sun.appserv]]" |#]
    [#|2010-10-23T17:37:34.915-0700|INFO|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=23;_ThreadName=Thread-1;|In main loop, we have serious trouble: java.lang.OutOfMemoryError: Java heap space|#]
    [#|2010-10-23T17:37:56.516-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=66;_ThreadName=Thread-1;|Exception in thread "pool-6-thread-7" |#]
    [#|2010-10-23T17:39:11.060-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=23;_ThreadName=Thread-1;|Exception in thread "{felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, service.pid=org.apache.felix.fileinstall.fd8877ce-71aa-41d2-8ddc-15ce996cde1b, felix.fileinstall.dir=/opt/glassfishv3/glassfish/domains/domain1/autodeploy/bundles/, felix.fileinstall.filename=org.apache.felix.fileinstall-autodeploy-bundles.cfg, service.factorypid=org.apache.felix.fileinstall, felix.fileinstall.debug=1}" |#]
    [#|2010-10-23T17:39:11.070-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=66;_ThreadName=Thread-1;|java.lang.OutOfMemoryError: Java heap space
         at java.util.IdentityHashMap.init(IdentityHashMap.java:261)
         at java.util.IdentityHashMap.<init>(IdentityHashMap.java:207)
         at com.sleepycat.je.utilint.IdentityHashMap.<init>(IdentityHashMap.java:25)
         at com.sleepycat.je.cleaner.LocalUtilizationTracker.<init>(LocalUtilizationTracker.java:39)
         at com.sleepycat.je.recovery.Checkpointer.flushDirtyNodes(Checkpointer.java:665)
         at com.sleepycat.je.recovery.Checkpointer.syncDatabase(Checkpointer.java:604)
         at com.sleepycat.je.dbi.DatabaseImpl.sync(DatabaseImpl.java:977)
         at com.sleepycat.je.dbi.DatabaseImpl.handleClosed(DatabaseImpl.java:863)
         at com.sleepycat.je.Database.closeInternal(Database.java:458)
         at com.sleepycat.je.Database.close(Database.java:314)
         at com.sleepycat.je.SecondaryDatabase.close(SecondaryDatabase.java:331)
         at com.sleepycat.persist.impl.Store.closeDb(Store.java:1454)
         at com.sleepycat.persist.impl.Store.close(Store.java:1059)
         at com.sleepycat.persist.EntityStore.close(EntityStore.java:630)
         at name.justinthomas.flower.analysis.persistence.FlowReceiver.addFlow(FlowReceiver.java:94)
         at name.justinthomas.flower.analysis.persistence.FlowReceiver.addFlow(FlowReceiver.java:65)
         at name.justinthomas.flower.collector.FlowWorker.parseData(FlowWorker.java:382)
         at name.justinthomas.flower.collector.FlowWorker.v9(FlowWorker.java:111)
         at name.justinthomas.flower.collector.FlowWorker.run(FlowWorker.java:61)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
         at java.lang.Thread.run(Thread.java:636)
    |#]
    [#|2010-10-23T17:39:11.124-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=23;_ThreadName=Thread-1;|java.lang.OutOfMemoryError: Java heap space
    |#]
    [#|2010-10-23T17:39:11.141-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=72;_ThreadName=Thread-1;|Exception in thread "pool-6-thread-3" |#]
    [#|2010-10-23T17:39:11.144-0700|SEVERE|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=72;_ThreadName=Thread-1;|java.lang.OutOfMemoryError: Java heap space
    |#]
    It's very frustrating, because things run so well at first and then just deteriorate into a resource nightmare. Any suggestions would be welcome. The application is running with 3 CPU cores and 2GB RAM.
    Edited by: justindthomas on Oct 23, 2010 7:19 PM: I initially tried to use the forum's "URL" mechanism, but that doesn't seem to work worth anything, so I un-did it.

    I've disabled that thread for now. While debugging that, I ran into a SecondaryIntegrityException and I read that I shouldn't use secondary indexes without also using transactions. I enabled transactional processing, but the locking issues grew far worse. I opted to find ways to not use secondary indexes instead.You're right that with secondaries it is important to use txns. But I'm not sure why you're having such severe locking problems with txns. Were you using a txn with a cursor, to perform a scan? If so, I can probably suggest ways of doing that without the txn, if you can describe what you're doing and/or point me to your source code. Or, perhaps you've decided not to use secondaries, and this isn't an issue anymore?
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • EBS 12.1.3 Upgrade issue

    Hi,
    I installed 12.1.1 with the Vision Database on my machines which has a 64 bit Linux 5 update 5 operating system and everything went fine. After that I decided to upgrade to 12.1.3. I installed the following patches in order they are given below :
    1) R12.AD.B.DELTA.3 Patch 9239089
    2) Patch 9239090
    3) Patch 9239095
    4) 9817770:R12.ATG_PF.B POST-R12.ATG_PF.B.DELTA.3CONSOLIDATED PATCH
    5) 9966055:R12.FND.B [TRANSLATED VERSION OF FNDSCSGN NOT LAUNCHED
    The only issues I had was during the compilation of one form library I got an error in Patch 923090 and I said to continue. The patches completed successfully (I think) since I can log into applications. My issue is I have a lot of invalid objects. I tried to manually compile them but failed then followed one of the other threads to run utlrp.sql and utlirp.sql scripts as per (R12.1.1 - Invalid Objects After Patching [ID 1093163.1])
    I have followed that document and tried to run but my invalid count stays the same. Here is the snapshot when I query the database :
    SQL> SELECT COUNT(*), OWNER FROM DBA_OBJECTS WHERE STATUS='INVALID'
    2 GROUP BY OWNER;
    COUNT(*) OWNER
    1 RE
    2 CA
    4 PUBLIC
    1 HERMAN
    228 APPS
    2 FLOWS_010500
    SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_BGN 2012-04-05 07:23:05
    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-04-05 07:24:29
    DECLARE
    ERROR at line 1:
    ORA-00904: "FALSE": invalid identifier
    ORA-06512: at line 13
    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
    4
    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
    4
    PL/SQL procedure successfully completed.
    Invoking Ultra Search Install/Upgrade validation procedure VALIDATE_WK
    Ultra Search VALIDATE_WK done with no error
    PL/SQL procedure successfully completed.
    However for some reason the job utlrp.sql only shows 4 invalids as shown when I run it. But the number changes once the script is finished and I am not sure why. If I query SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6) now after utlrp.sql has finished running I get the below
    SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    COUNT(*)
    234
    But if I query the same query while utlrp.sql is running I get a number as low as 10 I have seen but once the script finishes it goes back up. I don't know what to do. I have run autoconfig on both the db and apps tier. Is there anything anyone can suggest me ? I am totally lost on this.
    Thanks..

    Hi I did set the disablefast_validate=TRUE and re-ran only utlrp.sql to re-compile now I have a lot more packages compiled but I still have some invalids. I just want to know can I ignore these and move on or are they important packages / objects in APPS which may impact functionality ?
    below is the results of the invalid objects.
    Thanks
    OWNER,OBJECT_NAME,SUBOBJECT_NAME,OBJECT_ID,DATA_OBJECT_ID,OBJECT_TYPE,CREATED,LAST_DDL_TIME,TIMESTAMP,STATUS,TEMPORARY,GENERATED,SECONDARY,NAMESPACE,EDITION_NAME
    PUBLIC,WWV_FLOW_LIST_OF_VALUES_DATA,,1006661,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
    PUBLIC,WWV_FLOW_LISTS_OF_VALUES$,,1006663,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
    PUBLIC,WWV_FLOW_GENERIC,,1006687,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
    PUBLIC,WWV_FLOW_FIELD_TEMPLATES,,1006699,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
    RE,RE_PROFILER,,1207268,0,PACKAGE BODY,17-NOV-04,05-APR-12,2012-04-05:10:52:51,INVALID,N,N,N,2,
    HERMAN,RDT_1,,1713973,1713973,TABLE,18-JAN-06,18-JAN-06,2006-01-18:13:18:02,INVALID,N,N,N,1,
    APPS,XLA_00707_AAD_C_000026_PKG,,2362389,0,PACKAGE BODY,03-AUG-07,05-APR-12,2012-04-05:10:52:52,INVALID,N,N,N,2,
    APPS,XLA_20065_AAD_C_000030_PKG,,2370236,0,PACKAGE BODY,16-AUG-07,05-APR-12,2012-04-05:10:53:05,INVALID,N,N,N,2,
    APPS,FSAH_DUPLICATE_PKG,,2385307,0,PACKAGE BODY,23-AUG-07,05-APR-12,2012-04-05:10:53:08,INVALID,N,N,N,2,
    APPS,XLA_00707_AAD_C_000044_PKG,,2661674,0,PACKAGE BODY,14-JAN-08,05-APR-12,2012-04-05:10:53:08,INVALID,N,N,N,2,
    APPS,MSD_DEM_OBI_DEMANTRA_MV,,3255317,,MATERIALIZED VIEW,09-JUL-08,09-JUL-08,2008-07-09:09:14:28,INVALID,N,N,N,19,
    CA,F,,3260665,3260665,TABLE,24-SEP-08,24-SEP-08,2008-09-24:16:00:14,INVALID,N,N,N,1,
    CA,G,,3260683,3260683,TABLE,24-SEP-08,24-SEP-08,2008-09-24:16:00:15,INVALID,N,N,N,1,

  • Many db objects error after Upgrate EBS 12.1.1 to EBS 12.1.3

    Hi,
    recently we have upgraded our EBS from 12.1.1 to 12.1.3 and there are almost 777 invalid objects after recompiling using adadmin.
    I tried to recompile INVALID objects using utlrp.sql but I am getting below error.
    SQL> @utlrp.sql
    SELECT dbms_registry_sys.time_stamp('utlrp_bgn') as timestamp from dual
    ERROR at line 1:
    ORA-00904: "DBMS_REGISTRY_SYS"."TIME_STAMP": invalid identifier
    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>#
    DECLARE
    ERROR at line 1:
    ORA-04067: not executed, package body "APPS.UTL_RECOMP" does not exist
    ORA-06508: PL/SQL: could not find program unit being called: "APPS.UTL_RECOMP"
    ORA-06512: at line 4
    SELECT dbms_registry_sys.time_stamp('utlrp_end') as timestamp from dual
    ERROR at line 1:
    ORA-00904: "DBMS_REGISTRY_SYS"."TIME_STAMP": invalid identifier
    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>#
    select COUNT(*) "OBJECTS WITH ERRORS" from obj$ where status = 3
    ERROR at line 1:
    ORA-00942: table or view does not exist
    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>#
    select COUNT(*) "ERRORS DURING RECOMPILATION" from utl_recomp_errors
    ERROR at line 1:
    ORA-00942: table or view does not exist
    DECLARE
    ERROR at line 1:
    ORA-00942: table or view does not exist
    ORA-06512: at line 31
    BEGIN dbms_registry_sys.validate_components; END;
    ERROR at line 1:
    ORA-06550: line 1, column 7:
    PLS-00201: identifier 'DBMS_REGISTRY_SYS.VALIDATE_COMPONENTS' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Please advise for further.
    Thanks in advance,
    Nish

    950358 wrote:
    Thanks Husain,
    I have run utlrp.sql but still there 777 invalid objects available in my system.
    Please advise.
    Thanks,
    NishWhat is the error you get when you compile those objects?
    How many invalid objects you have under each schema?
    Please see old threads for the invalid objects MOS docs (after R12 upgrade and generic ones).
    https://forums.oracle.com/forums/search.jspa?threadID=&q=Invalid+AND+Objects+AND+12.1.3&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
    https://forums.oracle.com/forums/search.jspa?threadID=&q=Invalid+AND+Objects+AND+R12&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
    Thanks,
    Hussein

  • Upgrade database from 10.2.0.1.0 to 11.1.0.... I am not abble to upgrade.

    SQL> spool on
    SQL> spool 'preupgrade1.log'
    SQL> startup upgrade;
    ORA-32004: obsolete and/or deprecated parameter(s) specified
    ORACLE instance started.
    Total System Global Area 602619904 bytes
    Fixed Size 1348956 bytes
    Variable Size 226495140 bytes
    Database Buffers 369098752 bytes
    Redo Buffers 5677056 bytes
    Database mounted.
    Database opened.
    SQL> @E:\ORACLE11G\PRODUCT\11.1.0\product\11.1.0\db_1\RDBMS\ADMIN\utlu111i.sql;
    ERROR:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    DECLARE
    ERROR at line 1:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    ERROR:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    SQL> select count(*) from obj$ where owner#=0 AND type#=2 and name='PUIU$DBUA;
    ERROR:
    ORA-01756: quoted string not properly terminated
    SQL> select count(*) from obj$ where owner#=0 AND type#=2 and name='PUIU$DBUA';
    COUNT(*)
    0
    SQL> @/home/oracle/u01/app/oracle/product/11.1.0/db_1/rdbms/admin/utlrp.sql
    SP2-0310: unable to open file "/home/oracle/u01/app/oracle/product/11.1.0/db_1/r
    dbms/admin/utlrp.sql"
    SQL>
    SQL> @E:\ORACLE11G\product\11.1.0\product\11.1.0\db_1\rdbms\admin\utlrp.sql;
    SELECT dbms_registry_sys.time_stamp('utlrp_bgn') as timestamp from dual
    ERROR at line 1:
    ORA-04023: Object SYS.DBMS_REGISTRY_SYS could not be validated or authorized
    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>#
    DECLARE
    ERROR at line 1:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    SELECT dbms_registry_sys.time_stamp('utlrp_end') as timestamp from dual
    ERROR at line 1:
    ORA-04023: Object SYS.DBMS_REGISTRY_SYS could not be validated or authorized
    DECLARE
    ERROR at line 1:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    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
    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
    ERROR:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    DECLARE
    ERROR at line 1:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    BEGIN dbms_registry_sys.validate_components; END;
    ERROR at line 1:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    ERROR:
    ORA-04023: Object SYS.STANDARD could not be validated or authorized
    SQL>
    Edited by: user11958935 on Aug 12, 2010 2:21 AM
    In this issue what happened their? and what is the actual issue ? Pls provide the answer in step by step wise

    You need to run this script while using the 10g binaries. See http://download.oracle.com/docs/cd/B28359_01/server.111/b28300/upgrade.htm#UPGRD12395
    HTH
    Srini

  • While running utlrp in 11.2.0.2 database, errors are seen

    SQL> @utlrp.sql
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_BGN 2011-06-10 22:13:37
    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 2011-06-10 22:16:18
    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
    71
    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
    22
    Function created.
    PL/SQL procedure successfully completed.
    Function dropped.
    ORDIM registered 0 XML schemas.
    The following XML schemas are not registered:
    http://xmlns.oracle.com/ord/dicom/UIDdefinition_1_0
    http://xmlns.oracle.com/ord/dicom/anonymity_1_0
    http://xmlns.oracle.com/ord/dicom/attributeTag_1_0
    http://xmlns.oracle.com/ord/dicom/constraint_1_0
    http://xmlns.oracle.com/ord/dicom/datatype_1_0
    http://xmlns.oracle.com/ord/dicom/manifest_1_0
    http://xmlns.oracle.com/ord/dicom/mapping_1_0
    http://xmlns.oracle.com/ord/dicom/mddatatype_1_0
    http://xmlns.oracle.com/ord/dicom/metadata_1_0
    http://xmlns.oracle.com/ord/dicom/orddicom_1_0
    http://xmlns.oracle.com/ord/dicom/preference_1_0
    http://xmlns.oracle.com/ord/dicom/privateDictionary_1_0
    http://xmlns.oracle.com/ord/dicom/rpdatatype_1_0
    http://xmlns.oracle.com/ord/dicom/standardDictionary_1_0
    http://xmlns.oracle.com/ord/meta/dicomImage
    http://xmlns.oracle.com/ord/meta/exif
    http://xmlns.oracle.com/ord/meta/iptc
    http://xmlns.oracle.com/ord/meta/ordimage
    http://xmlns.oracle.com/ord/meta/xmp
    ORDIM DICOM repository has 0 documents.
    The following default DICOM repository documents are not installed:
    ordcman.xml
    ordcmcmc.xml
    ordcmcmd.xml
    ordcmct.xml
    ordcmmp.xml
    ordcmpf.xml
    ordcmpv.xml
    ordcmsd.xml
    ordcmui.xml
    PL/SQL procedure successfully completed.
    Please suggest .
    Regards

    I am also facing below issue while running UTLRP in 11.1.0.7
    SQL> Rem Run component validation procedure
    SQL> Rem =====================================================================
    SQL>
    SQL> EXECUTE dbms_registry_sys.validate_components;
    ORDIM INVALID OBJECTS: CODE_SEQUENCE253_T - 5 - 13
    ORDIM INVALID OBJECTS: CODE_SEQUENCE255_COLL - 5 - 13
    ORDIM INVALID OBJECTS: CODE_SQ254_T - 5 - 13
    ORDIM INVALID OBJECTS: ORD_DICOM_HEADER257_T - 5 - 13
    ORDIM INVALID OBJECTS: MEDIA_STORAGE_SOP_CLASS259_T - 5 - 13
    ORDIM INVALID OBJECTS: MEDIA_STORAGE_SOP_INSTA260_T - 5 - 13
    ORDIM INVALID OBJECTS: TRANSFER_SYNTAX_UID261_T - 5 - 13
    ORDIM INVALID OBJECTS: IMPLEMENTATION_CLASS_UI262_T - 5 - 13
    ORDIM INVALID OBJECTS: IMPLEMENTATION_VERSION_263_T - 5 - 13
    ORDIM INVALID OBJECTS: SOURCE_APPLICATION_ENTI264_T - 5 - 13
    ORDIM INVALID OBJECTS: FILE_META_HEADER258_T - 5 - 13
    ORDIM INVALID OBJECTS: NAME267_T - 5 - 13
    ORDIM INVALID OBJECTS: ID268_T - 5 - 13
    ORDIM INVALID OBJECTS: BIRTH_DATE269_T - 5 - 13
    ORDIM INVALID OBJECTS: SEX270_T - 5 - 13
    ORDIM INVALID OBJECTS: PATIENT266_T - 5 - 13
    ORDIM INVALID OBJECTS: INSTANCE_UID272_T - 5 - 13
    ORDIM INVALID OBJECTS: DATE273_T - 5 - 13
    ORDIM INVALID OBJECTS: TIME275_T - 5 - 13
    ORDIM registered 0 XML schemas.
    The following XML schemas are not registered:
    http://xmlns.oracle.com/ord/dicom/UIDdefinition_1_0
    http://xmlns.oracle.com/ord/dicom/anonymity_1_0
    http://xmlns.oracle.com/ord/dicom/constraint_1_0
    http://xmlns.oracle.com/ord/dicom/datatype_1_0
    http://xmlns.oracle.com/ord/dicom/mapping_1_0
    http://xmlns.oracle.com/ord/dicom/mddatatype_1_0
    http://xmlns.oracle.com/ord/dicom/metadata_1_0
    http://xmlns.oracle.com/ord/dicom/orddicom_1_0
    http://xmlns.oracle.com/ord/dicom/preference_1_0
    http://xmlns.oracle.com/ord/dicom/privateDictionary_1_0
    http://xmlns.oracle.com/ord/dicom/rpdatatype_1_0
    http://xmlns.oracle.com/ord/dicom/standardDictionary_1_0
    http://xmlns.oracle.com/ord/meta/dicomImage
    http://xmlns.oracle.com/ord/meta/exif
    http://xmlns.oracle.com/ord/meta/iptc
    http://xmlns.oracle.com/ord/meta/ordimage
    http://xmlns.oracle.com/ord/meta/xmp
    ORDIM DICOM repository has 0 documents.
    The following default DICOM repository documents are not installed:
    ordcman.xml
    ordcmcmc.xml
    ordcmcmd.xml
    ordcmct.xml
    ordcmmp.xml
    ordcmpf.xml
    ordcmpv.xml
    ordcmsd.xml
    ordcmui.xml
    Invoking Ultra Search Install/Upgrade validation procedure VALIDATE_WK
    Ultra Search VALIDATE_WK done with no error
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:01.09
    SQL> SET serveroutput off
    SQL>
    SQL>
    SQL> Rem ===========================================================================
    SQL> Rem END utlrp.sql
    SQL> Rem ===========================================================================
    Please suggest how to solve this.
    manually compilation also not helping
    Regards,
    -Ravi.

  • Delay in creation of idocs after business partner change

    Hello all,
    In our production CRM system, we had an issue where even though users were making changes/creation of business partners, there was no trigger for the creation of idocs to be sent to the middleware system (connected via ALE to the CRM system).
    This happened for a period of 17 minutes and then suddenly idocs started generating for the changes and posted to the middleware system as normal.
    There were no resource constraints in the system during that time.  We also checked the ORACLE database alert file to see if there were any database issues and found nothing.
    The main activity going on that time was the download of product/materials from our R/3 system. 
    We can confirm that bdocs were generated for the business partner change to be sent to R/3 and those were sent succesfully during these 17 minutes.  So only the creation of idocs were impacted.
    We are trying to determine root cause as to why for those 17 minutes, idocs were not getting created.
    Any help is appreciated.
    Thanks,
    Ramesh

    Hello Kiran,
    Thanks for the reply.  The issue really is why during those 17 minutes idocs were not generated for the business partner changes.
    After those 17 minutes, idocs started generating fine (even for those business partner changes that happened during those 17 minutes).
    So we are looking to find a root cause for this behavior.
    Thanks,
    Ramesh

  • E-mail from SAP R/3 to Outlook

    Hi,
    I am facing issues when attempting to send e-mails from SAP R/3 to Outlook it gives following error. E-mail id of the user id correct but for some reason but I still get these odd error/no message.
    There is no resource constraint from SAP R/3 side, I have even seen a case when both the e-mail ids(To & CC) were correct. It failed on CC and TO went successful and visa-versa.
    1. When E-mail is erroring out in SOST
    Internal error: No Send Order Generated. Error Code:NI_SREQ
    Internal error: No Send Order Generated. Error Code:NI_SREQ
    Message no. XS829
    Diagnosis
    An error occurred in program No Send Order Generated. Error Code:NI_SREQ
    Error text:
    Additional information:
    System Response
    Message processing terminated.
    Procedure
    Report the error to the SAP Hotline.
    Log :
    04/11/2007     10:30:28     Document sent
    04/11/2007     10:30:28     Wait for communications service
    04/11/2007     10:30:35     Internal error: No Send Order Generated. Error Code:NI_SREQ
    04/11/2007     10:30:36     Document deleted from queue
    2. When NO STATUS is updated in SAP - SOST.
    Recipient  Is Valid. Delivery Attempted
    Message no. XS718
    Diagnosis
    The communication system recognized the recipient  as valid and will send the message to this recipient, or will generate an appropriate status message if the message cannot be delivered.
    System Response
    Processing was completed normally.
    Additional information on the node used (in the system language of the node, if available):
    250 2.1.5 [email protected]
    Procedure
    No action is necessary.
    04/11/2007     11:00:41     Document sent
    04/11/2007     11:00:41     Wait for communications service
    04/11/2007     11:05:35     Recipient Is Valid. Delivery Attempted
    04/11/2007     11:05:35     Document deleted from queue
    Appreciate your help in resolving the issue.
    Thanks
    Nani

    Default domain is maintained.
    This issue is happening only with few users when they are trying to send a mail through some customized Z t-code.
    Recipient ................... Is Valid. Delivery Attempted.
    Message XS718.
    Pls advice.

  • After upgrading to 10.2.0.4

    Hi All,
    os: hp-ux
    upgrading from 9.2.0.4 to 10.2.0.4
    After running catupgrd.sql on my 9.2.0.4 database, i have seen some statements on my Alert log file.
    Please guide me what may be the reason for this lines.
    >
    Thread 1 advanced to log sequence 426 (LGWR switch)
    Current log# 2 seq# 426 mem# 0: /wup/oradata/wgmugpro/redo02.log
    Thu May 13 12:05:38 2010
    SERVER COMPONENT id=RDBMS: status=VALID, version=10.2.0.4.0, timestamp=2010-05-13 12:05:38
    Thu May 13 12:06:47 2010
    Some indexes or index [sub]partitions of table WMSYS.AQ$_WM$EVENT_QUEUE_TABLE_S have been marked unusable
    Thu May 13 12:06:48 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$ENV_VARS have been marked unusable
    Thu May 13 12:06:48 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$EVENTS_INFO have been marked unusable
    Thu May 13 12:06:48 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$HINT_TABLE have been marked unusable
    Thu May 13 12:06:49 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$NEXTVER_TABLE have been marked unusable
    Thu May 13 12:06:49 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$SYSPARAM_ALL_VALUES have been marked unusable
    Thu May 13 12:06:50 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$VERSION_HIERARCHY_TABLE have been marked unusable
    Thu May 13 12:06:50 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$WORKSPACES_TABLE have been marked unusable
    Thu May 13 12:06:50 2010
    Some indexes or index [sub]partitions of table WMSYS.WM$WORKSPACE_PRIV_TABLE have been marked unusable
    Thu May 13 12:06:54 2010
    SERVER COMPONENT id=OWM: status=VALID, version=10.2.0.4.3, timestamp=2010-05-13 12:06:54
    Thu May 13 12:07:45 2010
    SERVER ACTION=UPGRADE id=: Upgraded from 9.2.0.4.0
    SERVER COMPONENT id=UPGRD_END: timestamp=2010-05-13 12:07:45
    >
    i ran the postupgradation tool and it is showing all are valid like below
    >
    Oracle Database 10.2 Upgrade Status Utility 05-13-2010 12:13:52
    Component Status Version HH:MM:SS
    Oracle Database Server VALID 10.2.0.4.0 00:16:31
    Oracle Workspace Manager VALID 10.2.0.4.3 00:01:15
    Total Upgrade Time: 00:18:37
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.01
    >
    Thanks and Regards
    Vamshi

    Hi Admin,
    after running the utlrp.sql
    >
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:16.08
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_END 2010-05-13 12:39:15
    Elapsed: 00:00:00.00
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.02
    12:39:15 DOC> The following query reports the number of objects that have compiled
    12:39:15 DOC> with errors (objects that compile with errors have status set to 3 in
    12:39:15 DOC> obj$). If the number is higher than expected, please examine the error
    12:39:15 DOC> messages reported with each object (using SHOW ERRORS) to see if they
    12:39:15 DOC> point to system misconfiguration or resource constraints that must be
    12:39:15 DOC> fixed before attempting to recompile these objects.
    12:39:15 DOC>#
    OBJECTS WITH ERRORS
    0
    Elapsed: 00:00:00.03
    12:39:15 DOC> The following query reports the number of errors caught during
    12:39:15 DOC> recompilation. If this number is non-zero, please query the error
    12:39:15 DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    12:39:15 DOC> are due to misconfiguration or resource constraints that must be
    12:39:15 DOC> fixed before objects can compile successfully.
    12:39:15 DOC>#
    ERRORS DURING RECOMPILATION
    0
    Elapsed: 00:00:00.00
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.14
    >
    12:39:15 SQL> select index_name,status ,owner from dba_indexes where status!='VALID';
    INDEX_NAME                     STATUS   OWNER
    WRH$_SERVICE_WAIT_CLASS_PK     N/A      SYS
    WRH$_SERVICE_STAT_PK           N/A      SYS
    WRH$_TABLESPACE_STAT_PK        N/A      SYS
    WRH$_ACTIVE_SESSION_HISTORY_PK N/A      SYS
    WRH$_INST_CACHE_TRANSFER_PK    N/A      SYS
    WRH$_DLM_MISC_PK               N/A      SYS
    WRH$_SEG_STAT_PK               N/A      SYS
    WRH$_PARAMETER_PK              N/A      SYS
    WRH$_OSSTAT_PK                 N/A      SYS
    WRH$_SYS_TIME_MODEL_PK         N/A      SYS
    WRH$_SYSSTAT_PK                N/A      SYS
    WRH$_SGASTAT_U                 N/A      SYS
    WRH$_ROWCACHE_SUMMARY_PK       N/A      SYS
    WRH$_DB_CACHE_ADVICE_PK        N/A      SYS
    WRH$_LATCH_MISSES_SUMMARY_PK   N/A      SYS
    WRH$_LATCH_PARENT_PK           N/A      SYS
    WRH$_LATCH_CHILDREN_PK         N/A      SYS
    WRH$_LATCH_PK                  N/A      SYS
    WRH$_WAITSTAT_PK               N/A      SYS
    WRH$_SYSTEM_EVENT_PK           N/A      SYS
    WRH$_SQLSTAT_INDEX             N/A      SYS
    WRH$_SQLSTAT_PK                N/A      SYS
    WRH$_FILESTATXS_PK             N/A      SYS
    I_STREAMS_APPLY_SPILL_MSGS_PT1 N/A      SYS
    SYS_IL0000320867C00008$$       N/A      SYS
    LOGMNRC_I3GTLO                 N/A      SYSTEM
    LOGMNRC_I2GTLO                 N/A      SYSTEM
    LOGMNRC_GTCS_PK                N/A      SYSTEM
    LOGMNR_I2INDPART$              N/A      SYSTEM
    LOGMNR_I1INDCOMPART$           N/A      SYSTEM
    LOGMNR_I1INDSUBPART$           N/A      SYSTEM
    LOGMNR_I1INDPART$              N/A      SYSTEM
    LOGMNR_I1ATTRCOL$              N/A      SYSTEM
    LOGMNR_I2COL$                  N/A      SYSTEM
    LOGMNR_I1COL$                  N/A      SYSTEM
    LOGMNR_I1TS$                   N/A      SYSTEM
    LOGMNR_I2TAB$                  N/A      SYSTEM
    LOGMNR_I1TAB$                  N/A      SYSTEM
    LOGMNR_I1USER$                 N/A      SYSTEM
    LOGMNRC_I2GTCS                 N/A      SYSTEM
    LOGMNR_I1LOBFRAG$              N/A      SYSTEM
    LOGMNR_I1ICOL$                 N/A      SYSTEM
    LOGMNR_I2IND$                  N/A      SYSTEM
    LOGMNR_I2TABSUBPART$           N/A      SYSTEM
    LOGMNR_I2TABCOMPART$           N/A      SYSTEM
    LOGMNR_I2TABPART$              N/A      SYSTEM
    LOGMNR_I1CCOL$                 N/A      SYSTEM
    LOGMNR_I1CDEF$                 N/A      SYSTEM
    LOGMNR_I1LOB$                  N/A      SYSTEM
    LOGMNR_I1COLTYPE$              N/A      SYSTEM
    LOGMNR_I1TYPE$                 N/A      SYSTEM
    LOGMNR_I1IND$                  N/A      SYSTEM
    LOGMNR_I1TABCOMPART$           N/A      SYSTEM
    LOGMNR_I1TABSUBPART$           N/A      SYSTEM
    LOGMNR_I1TABPART$              N/A      SYSTEM
    LOGMNRC_GSII_PK                N/A      SYSTEM
    LOGMNRC_GTLO_PK                N/A      SYSTEM
    LOGMNR_I1OBJ$                  N/A      SYSTEM
    58 rows selected.
    Elapsed: 00:00:00.16still it is showing in dba_indexes.

  • EXPDP Error in Oracle 11.2.0.1.0

    Hello Team,
    I have a problem in executing expdp/impdp in oracle version 11.2.0.1.0. Following is the error output. Traditional exp/imp is working fine.
    Note: command executed on Oracle Linux on VMware
    [oracle1@rac1 test]$ expdp
    Export: Release 11.2.0.1.0 - Production on Mon Aug 12 15:29:39 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    Username: system
    Password:
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORA-31626: job does not exist
    ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
    ORA-06512: at "SYS.KUPV$FT", line 991
    ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
    Regards,

    Hello DK2010,
    =======================================================================================================
    SQL> set lines 100
    SQL> set pagesize 200
    SQL> /
    OWNER                          OBJECT_TYPE
    OBJECT_NAME
    OBJECT_ID STATUS
    SYS                            PACKAGE
    DBMS_INTERNAL_LOGSTDBY
          5067 VALID
    SYS                            PACKAGE BODY
    DBMS_INTERNAL_LOGSTDBY
         10780 INVALID
    ===================================================================================================
    UTLRP.SQL output:
    ====================================================================================================
    SQL> @utlrp.sql
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_BGN  2013-08-12 16:03:24
    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>#
    DECLARE
    ERROR at line 1:
    ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
    ORA-06512: at "SYS.UTL_RECOMP", line 781
    ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
    ORA-06512: at line 4
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_END  2013-08-12 16:03:25
    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
                     13
    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
    PL/SQL procedure successfully completed.
    SQL> SELECT owner, object_type, object_name, object_id, status FROM SYS.dba_objects where object_name = 'DBMS_INTERNAL_LOGSTDBY';
    OWNER                          OBJECT_TYPE
    OBJECT_NAME
    OBJECT_ID STATUS
    SYS                            PACKAGE
    DBMS_INTERNAL_LOGSTDBY
          5067 VALID
    SYS                            PACKAGE BODY
    DBMS_INTERNAL_LOGSTDBY
         10780 INVALID
    ==================================================
    SELECT owner,object_type,object_name,status FROM dba_objects WHERE  status = 'INVALID' ORDER BY owner, object_type, object_name;SQL> SQL>
    OWNER                          OBJECT_TYPE         OBJECT_NAME                    STATUS
    DBSNMP                         PACKAGE             BSLN                           INVALID
    DBSNMP                         PACKAGE             BSLN_INTERNAL                  INVALID
    DBSNMP                         PACKAGE BODY        BSLN                           INVALID
    DBSNMP                         PACKAGE BODY        BSLN_INTERNAL                  INVALID
    DBSNMP                         SYNONYM             MGMT_BSLN                      INVALID
    PUBLIC                         SYNONYM             DBA_LOGSTDBY_LOG               INVALID
    PUBLIC                         SYNONYM             DBMS_ADVISOR                   INVALID
    PUBLIC                         SYNONYM             DBMS_SQLPA                     INVALID
    PUBLIC                         SYNONYM             DBMS_SQLTUNE                   INVALID
    SYS                            FUNCTION            LOGSTDBY$TABF                  INVALID
    SYS                            FUNCTION            LOGSTDBY$UTABF                 INVALID
    SYS                            PACKAGE             DBMS_ADVISOR                   INVALID
    SYS                            PACKAGE             DBMS_SQLDIAG_INTERNAL          INVALID
    SYS                            PACKAGE             DBMS_SQLPA                     INVALID
    SYS                            PACKAGE             DBMS_SQLTUNE                   INVALID
    SYS                            PACKAGE             DBMS_SQLTUNE_INTERNAL          INVALID
    SYS                            PACKAGE             PRVT_ADVISOR                   INVALID
    SYS                            PACKAGE BODY        AS_REPLAY                      INVALID
    SYS                            PACKAGE BODY        DBMS_ADDM                      INVALID
    SYS                            PACKAGE BODY        DBMS_ADVISOR                   INVALID
    SYS                            PACKAGE BODY        DBMS_APPLY_ERROR               INVALID
    SYS                            PACKAGE BODY        DBMS_ARCH_PROVIDER_INTL        INVALID
    SYS                            PACKAGE BODY        DBMS_ASH_INTERNAL              INVALID
    SYS                            PACKAGE BODY        DBMS_AUTOTASK_PRVT             INVALID
    SYS                            PACKAGE BODY        DBMS_AUTO_TASK_EXPORT          INVALID
    SYS                            PACKAGE BODY        DBMS_CAPTURE_SWITCH_ADM        INVALID
    SYS                            PACKAGE BODY        DBMS_CAPTURE_SWITCH_INTERNAL   INVALID
    SYS                            PACKAGE BODY        DBMS_COMPRESSION               INVALID
    SYS                            PACKAGE BODY        DBMS_DBFS_CONTENT_ADMIN        INVALID
    SYS                            PACKAGE BODY        DBMS_DBFS_HS                   INVALID
    SYS                            PACKAGE BODY        DBMS_FEATURE_USAGE             INVALID
    SYS                            PACKAGE BODY        DBMS_FEATURE_USAGE_INTERNAL    INVALID
    SYS                            PACKAGE BODY        DBMS_INTERNAL_LOGSTDBY         INVALID
    SYS                            PACKAGE BODY        DBMS_ISCHED                    INVALID
    SYS                            PACKAGE BODY        DBMS_LOGREP_EXP                INVALID
    SYS                            PACKAGE BODY        DBMS_LOGSTDBY                  INVALID
    SYS                            PACKAGE BODY        DBMS_MANAGEMENT_PACKS          INVALID
    SYS                            PACKAGE BODY        DBMS_PROPAGATION_INTERNAL      INVALID
    SYS                            PACKAGE BODY        DBMS_REPORT                    INVALID
    SYS                            PACKAGE BODY        DBMS_SERVER_ALERT              INVALID
    SYS                            PACKAGE BODY        DBMS_SERVER_ALERT_PRVT         INVALID
    SYS                            PACKAGE BODY        DBMS_SMB                       INVALID
    SYS                            PACKAGE BODY        DBMS_SMB_INTERNAL              INVALID
    SYS                            PACKAGE BODY        DBMS_SPACE                     INVALID
    SYS                            PACKAGE BODY        DBMS_SPM                       INVALID
    SYS                            PACKAGE BODY        DBMS_SPM_INTERNAL              INVALID
    SYS                            PACKAGE BODY        DBMS_SQLDIAG                   INVALID
    SYS                            PACKAGE BODY        DBMS_SQLDIAG_INTERNAL          INVALID
    SYS                            PACKAGE BODY        DBMS_SQLPA                     INVALID
    SYS                            PACKAGE BODY        DBMS_SQLTCB_INTERNAL           INVALID
    SYS                            PACKAGE BODY        DBMS_SQLTUNE                   INVALID
    SYS                            PACKAGE BODY        DBMS_SQLTUNE_INTERNAL          INVALID
    SYS                            PACKAGE BODY        DBMS_SQLTUNE_UTIL1             INVALID
    SYS                            PACKAGE BODY        DBMS_SQLTUNE_UTIL2             INVALID
    SYS                            PACKAGE BODY        DBMS_STATS                     INVALID
    SYS                            PACKAGE BODY        DBMS_STATS_INTERNAL            INVALID
    SYS                            PACKAGE BODY        DBMS_STREAMS_ADM               INVALID
    SYS                            PACKAGE BODY        DBMS_STREAMS_ADM_UTL           INVALID
    SYS                            PACKAGE BODY        DBMS_STREAMS_AUTO_INT          INVALID
    SYS                            PACKAGE BODY        DBMS_STREAMS_SM                INVALID
    SYS                            PACKAGE BODY        DBMS_SWRF_INTERNAL             INVALID
    SYS                            PACKAGE BODY        DBMS_SWRF_REPORT_INTERNAL      INVALID
    SYS                            PACKAGE BODY        DBMS_UNDO_ADV                  INVALID
    SYS                            PACKAGE BODY        DBMS_WORKLOAD_CAPTURE          INVALID
    SYS                            PACKAGE BODY        DBMS_WORKLOAD_REPLAY           INVALID
    SYS                            PACKAGE BODY        DBMS_WORKLOAD_REPOSITORY       INVALID
    SYS                            PACKAGE BODY        DBMS_WRR_INTERNAL              INVALID
    SYS                            PACKAGE BODY        DBMS_XPLAN                     INVALID
    SYS                            PACKAGE BODY        HM_SQLTK_INTERNAL              INVALID
    SYS                            PACKAGE BODY        LOGMNR_DICT_CACHE              INVALID
    SYS                            PACKAGE BODY        PRVT_ACCESS_ADVISOR            INVALID
    SYS                            PACKAGE BODY        PRVT_ADVISOR                   INVALID
    SYS                            PACKAGE BODY        PRVT_COMPRESSION               INVALID
    SYS                            PACKAGE BODY        PRVT_HDM                       INVALID
    SYS                            PACKAGE BODY        PRVT_PARTREC_NOPRIV            INVALID
    SYS                            PACKAGE BODY        PRVT_REPORT_TAGS               INVALID
    SYS                            PACKAGE BODY        PRVT_SQLADV_INFRA              INVALID
    SYS                            PACKAGE BODY        PRVT_SQLPA                     INVALID
    SYS                            PACKAGE BODY        PRVT_SQLPROF_INFRA             INVALID
    SYS                            PACKAGE BODY        PRVT_SQLSET_INFRA              INVALID
    SYS                            PACKAGE BODY        PRVT_SYS_TUNE_MVIEW            INVALID
    SYS                            PACKAGE BODY        PRVT_TUNE_MVIEW                INVALID
    SYS                            PACKAGE BODY        PRVT_WORKLOAD                  INVALID
    SYS                            PACKAGE BODY        PRVT_WORKLOAD_NOPRIV           INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_AUM               INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_AUTOSTA           INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_AWR               INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_REGISTER_ALLFEAT  INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_SEGADV_USER       INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES1        INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES2        INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES3        INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES4        INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_WCR_CAPTURE       INVALID
    SYS                            PROCEDURE           DBMS_FEATURE_WCR_REPLAY        INVALID
    SYS                            PROCEDURE           LOGMNR_KRVRDA_TEST_APPLY       INVALID
    SYS                            TYPE                SCHEDULER$_REMOTE_ARG          INVALID
    SYS                            TYPE                SCHEDULER$_REMOTE_ARG_LIST     INVALID
    SYS                            TYPE                SCHEDULER$_REMOTE_DB_JOB_INFO  INVALID
    SYS                            TYPE BODY           WRI$_ADV_ABSTRACT_T            INVALID
    SYS                            TYPE BODY           WRI$_ADV_COMPRESSION_T         INVALID
    SYS                            TYPE BODY           WRI$_ADV_HDM_T                 INVALID
    SYS                            TYPE BODY           WRI$_ADV_OBJSPACE_TREND_T      INVALID
    SYS                            TYPE BODY           WRI$_ADV_SQLACCESS_ADV         INVALID
    SYS                            TYPE BODY           WRI$_ADV_SQLTUNE               INVALID
    SYS                            TYPE BODY           WRI$_ADV_TUNEMVIEW_ADV         INVALID
    SYS                            TYPE BODY           WRI$_REPT_PLAN_DIFF            INVALID
    SYS                            TYPE BODY           WRI$_REPT_SQLMONITOR           INVALID
    SYS                            TYPE BODY           WRI$_REPT_SQLPI                INVALID
    SYS                            TYPE BODY           WRI$_REPT_SQLT                 INVALID
    SYS                            VIEW                AQ$AQ_PROP_TABLE_R             INVALID
    SYS                            VIEW                AQ$SCHEDULER$_EVENT_QTAB_R     INVALID
    SYS                            VIEW                AQ$SCHEDULER$_REMDB_JOBQTAB    INVALID
    SYS                            VIEW                AQ$SCHEDULER$_REMDB_JOBQTAB_R  INVALID
    SYS                            VIEW                AQ$SCHEDULER_FILEWATCHER_QT_R  INVALID
    SYS                            VIEW                AQ$_AQ$_MEM_MC_F               INVALID
    SYS                            VIEW                AQ$_AQ_PROP_TABLE_F            INVALID
    SYS                            VIEW                AQ$_SCHEDULER$_EVENT_QTAB_F    INVALID
    SYS                            VIEW                AQ$_SCHEDULER$_REMDB_JOBQTAB_F INVALID
    SYS                            VIEW                AQ$_SCHEDULER_FILEWATCHER_QT_F INVALID
    SYS                            VIEW                DBA_LOGSTDBY_LOG               INVALID
    121 rows selected.
    =================================================================================================================
    How do i fix this invalid sys objects.
    Regards,

Maybe you are looking for