Repository disappeared....
I develop a repository manager and deploy it on the potal, then I create a repostory according to the repository manager in System config , and I even can see the repository in Monitor....but I can not see it in content manager ....wanna know why?
Can any on kindly help me, thanks in advance!
Hi
There seems to be problem in your indexing.
You need to restart system and again create a new Repository.
Thanks
Puneet
Similar Messages
-
KM repository disappears when reboot the portal server
Hi gurus
I develop a repository manager for a database like example from thilo, work fine but when i reboot the portal 7.0 sp 15 and go Portal content->km content-> in root, my repository disappears, i need re-deploy and re-index again
any idea
the only clue is this parto of the log
My repository name is /jdbc
*#1.5 #001143302F1E005E00000499000014D0000464696071349F#1236303659221#com.sapportals.wcm.service.indexmanagement.IndexService#sap.com/irj#com.sapportals.wcm.service.indexmanagement.IndexService#ANON1#0##n/a##4c5c3a8009ef11decd9e001143302f1e#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Error while registering for index relevant events: Invalid RID: No repository manager found for prefix: /jdbc - com.sapportals.wcm.repository.ResourceException: Invalid RID: No repository manager found for prefix: /jdbc*
** at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:399)** at java.lang.Throwable.<init>(Throwable.java:195)
at java.lang.Exception.<init>(Exception.java:41)
at com.sapportals.wcm.WcmException.<init>(WcmException.java:78)
at com.sapportals.wcm.WcmException.<init>(WcmException.java:74)
at com.sapportals.wcm.util.content.ContentException.<init>(ContentException.java:42)
at com.sapportals.wcm.repository.ResourceException.<init>(ResourceException.java:249)
at com.sapportals.wcm.repository.runtime.CmAdapter.getRepositoryManager(CmAdapter.java:511)
at com.sapportals.wcm.service.indexmanagement.IndexService.registerEvents(IndexService.java:3511)
at com.sapportals.wcm.service.indexmanagement.IndexService.startUpImpl(IndexService.java:3362)
at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.repository.runtime.CmAdapter.getService(CmAdapter.java:605)
at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.getIndexService(TaxonomyRepositoryManager.java:805)
at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.startUpImpl(TaxonomyRepositoryManager.java:699)
at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.repository.runtime.CmAdapter.getAllRepositoryManagers(CmAdapter.java:430)
at com.sapportals.wcm.service.urimapper.UriMapperPersistence.init(UriMapperPersistence.java:81)
at com.sapportals.wcm.service.urimapper.UriMapperService.startUpImpl(UriMapperService.java:366)
at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:216)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001143302F1E005E0000049A000014D000046469607152EA#1236303659237#com.sapportals.wcm.crt.CrtThreadSafeComponentHandler#sap.com/irj#com.sapportals.wcm.crt.CrtThreadSafeComponentHandler#ANON1#0##n/a##4c5c3a8009ef11decd9e001143302f1e#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###cyclic dependency during startup detected, see stack trace: com.sapportals.wcm.crt.ConstructionException: already starting component: class=com.sapportals.wcm.service.indexmanagement.IndexService, uri=crt://runtime/services/IndexmanagementService
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToConfigure(CrtThreadSafeComponentHandler.java:196)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:108)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.repository.runtime.CmAdapter.getService(CmAdapter.java:605)
at com.sapportals.wcm.service.indexmanagement.IndexService.logToApplog(IndexService.java:3542)
at com.sapportals.wcm.service.indexmanagement.IndexService.registerEvents(IndexService.java:3516)
at com.sapportals.wcm.service.indexmanagement.IndexService.startUpImpl(IndexService.java:3362)
at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.repository.runtime.CmAdapter.getService(CmAdapter.java:605)
at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.getIndexService(TaxonomyRepositoryManager.java:805)
at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.startUpImpl(TaxonomyRepositoryManager.java:699)
at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.repository.runtime.CmAdapter.getAllRepositoryManagers(CmAdapter.java:430)
at com.sapportals.wcm.service.urimapper.UriMapperPersistence.init(UriMapperPersistence.java:81)
at com.sapportals.wcm.service.urimapper.UriMapperService.startUpImpl(UriMapperService.java:366)
at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:216)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
thanks
salvatoreHI
check these links:
https://wiki.sdn.sap.com/wiki/display/KMC/KM%20content%20is%20unavailable%20-%20not%20able%20to%20view%20any%20repositories
https://wiki.sdn.sap.com/wiki/display/KMC/KMCConfigurationLost
SAP Note 1000351
Regards
Shridhar Gowda -
Flex Objects disappearing automatically from QTP Object repository
Application : Flex 3
Automation Tool: QTP 10
Plug-ins installed - Flex 3.0.0
Whenever we try to add the flex objects in our application to QTP Object repository, the same is getting analyzed, added and gets disappeared automatically in seconds.
Could there be a reason for this, we tried to uninstall & reinstall all plug-in & QTP as well. Still issue persists.
Please help.Hi
I am facing the same issue; but for our application. I am able to work fine with other Flex application, the issue is with only one application.
Is there any reason or solution to this. Please advice.
Thanks
Komala -
WebDav Repository Manager Disappears???
Hello,
I am seeing some strange behavior with an IIS WebDAV based KM WebDAV repository manager I created. I used the following as a basis for my setup.
http://help.sap.com/saphelp_nw04/helpdata/en/4a/217fb6c33c6748a1715a161ac942cd/frameset.htm
I created the memory cache, CM HTTP System, a portal system aliased with the same ID as the CM system, and finally the WebDAV Repository manager. If further setting detail is needed I can send that. The repository worked on Friday. It is not there today. This has happened twice. When I drill down into Content Administration > KM Content>root > runtime > Repository Managers... > IISWD > servers I am presented with "hostname". When I select Details>Properties>Miscellaneous tab I see failures.
Example:
last-failure-1: 2007-07-16T20:12:14Z: PROPFIND /ExternalPortal: com.sapportals.wcm.WcmException: sending request to: http://hostname/ request uri: /ExternalPortal unable to connect to hostname: unknown host: hostname (java.net.UnknownHostException: hostname)
All of the required KM objects mentioned before are still present and configured as they were a few days ago. Is my repository loosing it's reference to the CM HTTP System.? Has anyone seen this before?
Thanks,
DougHi Doug
I believe the problem is that your HTTP System in the portal cannot see the share you are trying to integrate into the potal. Is it a webdav-share set up using an IIS?
I have tried to implement the WebDAV/SSO solution where we got the same error for no reason. But after installing some different hotfixes (http://support.microsoft.com/default.aspx?scid=kb;en-us;893246, eg) and changing server to a standalone IIS, the error didn't occur any more.
Hope that can give you some ideas.
Kind regards,
Martin -
Repository objects disappeared
Hi to all,
we were working in OWB many months, and we didn't find any error, but today, while we were working, when we deploy one mapping, owb was closed.
Now, when we try to connect to the repository, OWB says that the repository associated to user doesn't exists.
May you help me to recover all objects?
Thanks!!!
Edited by: user8984874 on 16-may-2011 4:41If you have the OWB projects's backup as mdl file then you can create a new OWB repository and import those mdl and you will have the OWB design metadata . But you will loose the runtime information i.e execution , deployment .
-
Re: Disappearing changes in Repository
Geoffrey,
We have run into this problem as well. It seemed to happen when we checked out
some components edited them, saved the workspace multiple times, and then later
in the same Forte session received a "Hose 15 Error" which makes the workspace
read only. If we then exit the Forte session and start a new one, our changes
are
still there, but after we integrate that workspace the next time, the changes
will be
lost (just like you described). We also noticed that after the "Hose" error,
another
developer in a different workspace is able to check out the same components!
We have reported this to Forte tech support, but it is very hard to duplicate...
Good luck,
Derk
Hi fellow Forte users,
Recently I came across a most troubling event with Forte's repository change
management.
There were changes made to some components and afterwards the command to
integrate these changes was invoked. Seems pretty straight forward... Forte
popped up the ever-familiar "Integration successful" and the log even boasts
that the changes were successfully integrated. Immediately thereafter the
workspace was deleted since it was no longer needed.
However, when one tries to retrieve these components that were "successfully
integrated" the integrated changes are no longer there. All the work that
was done and 'successfully integrated' is gone!!
Even though the repository sometimes creeps close to a GIG of allocated disk
space I wouldn't think that this should be a problem since change management
reliability must never be compromised under any circumstances. The server
where the Forte repository resides has enough free hard disk space.
Has anyone encountered a problem like this?
Take care,
Geoff Whittington
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Geoffrey,
We have run into this problem as well. It seemed to happen when we checked out
some components edited them, saved the workspace multiple times, and then later
in the same Forte session received a "Hose 15 Error" which makes the workspace
read only. If we then exit the Forte session and start a new one, our changes
are
still there, but after we integrate that workspace the next time, the changes
will be
lost (just like you described). We also noticed that after the "Hose" error,
another
developer in a different workspace is able to check out the same components!
We have reported this to Forte tech support, but it is very hard to duplicate...
Good luck,
Derk
Hi fellow Forte users,
Recently I came across a most troubling event with Forte's repository change
management.
There were changes made to some components and afterwards the command to
integrate these changes was invoked. Seems pretty straight forward... Forte
popped up the ever-familiar "Integration successful" and the log even boasts
that the changes were successfully integrated. Immediately thereafter the
workspace was deleted since it was no longer needed.
However, when one tries to retrieve these components that were "successfully
integrated" the integrated changes are no longer there. All the work that
was done and 'successfully integrated' is gone!!
Even though the repository sometimes creeps close to a GIG of allocated disk
space I wouldn't think that this should be a problem since change management
reliability must never be compromised under any circumstances. The server
where the Forte repository resides has enough free hard disk space.
Has anyone encountered a problem like this?
Take care,
Geoff Whittington
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
Disappearing changes in Repository
Hi fellow Forte users,
Recently I came across a most troubling event with Forte's repository change
management.
There were changes made to some components and afterwards the command to
integrate these changes was invoked. Seems pretty straight forward... Forte
popped up the ever-familiar "Integration successful" and the log even boasts
that the changes were successfully integrated. Immediately thereafter the
workspace was deleted since it was no longer needed.
However, when one tries to retrieve these components that were "successfully
integrated" the integrated changes are no longer there. All the work that
was done and 'successfully integrated' is gone!!
Even though the repository sometimes creeps close to a GIG of allocated disk
space I wouldn't think that this should be a problem since change management
reliability must never be compromised under any circumstances. The server
where the Forte repository resides has enough free hard disk space.
Has anyone encountered a problem like this?
Take care,
Geoff Whittington
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Hi fellow Forte users,
Recently I came across a most troubling event with Forte's repository change
management.
There were changes made to some components and afterwards the command to
integrate these changes was invoked. Seems pretty straight forward... Forte
popped up the ever-familiar "Integration successful" and the log even boasts
that the changes were successfully integrated. Immediately thereafter the
workspace was deleted since it was no longer needed.
However, when one tries to retrieve these components that were "successfully
integrated" the integrated changes are no longer there. All the work that
was done and 'successfully integrated' is gone!!
Even though the repository sometimes creeps close to a GIG of allocated disk
space I wouldn't think that this should be a problem since change management
reliability must never be compromised under any circumstances. The server
where the Forte repository resides has enough free hard disk space.
Has anyone encountered a problem like this?
Take care,
Geoff Whittington
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
How can I config a yum plublic repository for VM support without paying ?
Please see:
yum plublic repository
I'm a bit confused with the options for support/updates. There is an option to get a VM support, which includes support, and a ULN subscription. There is also the option in the pricing guide to just get the ULN subscription, which is 1/3 the cost. Could I not get updates for OVM server/manager that way? I don't currently care to get support. I just want the updated binary RPMs.
I'm actually just trying to evaluate OVM 3.1.1 and so far it's junk because of several storage related issues I'm running in to. However, based on forum posts, I think most of those have been patched, but not released to the general public. How am I supposed to make an informed decision without committing $$$?
M.There was some NFS issue that was resolved. I don't have details available at this minute, but off the top of my head I started to create a virtual disk for a new VM, and it timed out after 10minutes. Even though it times out, it does actually create the image file, and that part is done nearly instantly, so I don't know why the timeout after 10 minutes. However, even though the image file is created it doesn't appear usable in the manager.
The storage is on an NFS server connected via direct 10GbE. This worked fine in 3.0.3, when I tested that version.
Based on the above post, my plan for now is to subscribe to ULN, and get/apply the updates, then post specific questions/details regarding the issue (unless it magically disappears with the patches).
Thanks,
M. -
9.0.2.6 Portal Repository Upgrade Patch problems.
We got some problem with Portal when tryed to apply
9.0.2.6 Upgrade. Could anybody give advice on this issue:
Initial configuration:
Solaris8, Portal 9.0.2.2.14, Oracle 9iAS R2 v.9.0.2.0, RDBMS 9.0.1.3. The infrastructure and midtier work on different SPARC-servers.
Accordingly upgrade procedure we succesfully applied:
a) Infrastructure: 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server
migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core.
b) 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core, Portal 9.0.2.6
patch.
After this we needed to make just one last step:
Portal 9.0.2.6 Repository Upgrade Patch (2981297) for
changing Portal's repository schemes. It worked but
like a result we got the next errors after patch upgrade
was done:
a) "The following invalid non-Portal objects exist in the Portal Schema: INDEX ABC (the name of portal object), PACKAGE BODY WWMON_REP_REPOSITORY, PACKAGE BODY WWMON_REP_REPOSIT_DTL, PLS-00103: Encountered the symbol "," when expecting one of the following: (-+case mod not null <an identifier>,...) The symbol "null" was substituted for "," to continue.)" See upgtmp/nonportal.log
b) "ERROR: 1 invalid objects remain; ERROR: Failed while updating the new portlet IDS..."
c) "ERROR: ORA-01407: cannot update ("PORTAL"."WWSBR_URL$"."URL") to NULL.
d) Two package body of packages at PORTAL scheme became invalid: WWMON_REP_REPOSITORY, WWMON_REP_REPOSIT_DTL. About 20 package body of packages at PORTAL_DEMO became invalid (It seems like initial portlet ID's disappeared
and except of pportlet_id there is nothing:
Example:
inital statement at body:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => 1065753336,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
after upgrade repository patch:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => ,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Like a result after 9.0.2.6 Portal Repository Upgrade Patch application we lost the possibility to edit user's
profiles at Portal and other nesessary features. It seems
like some portlet ID's just dissapeared from Portal scheme. Could anybody had the same problem with Portal Upgrade 9.0.2.6? Quite possible that we missed some important element at during upgrade but ,really, we didn't wait so unlucky result. Advice something, please...
Regards. Igor.Igor,
Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
Regards -
How to restrict permissions of fields in a repository file?
Hi Everybody,
I am trying to restrict permissions to fields in the repository file without affecting existing reports/dashboards.
When I restrict access to a variable (e.g. Job Requisition) it disappears from the available fields in the application, but the following error message appears when opening a analysis that uses that field:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 27005] Unresolved column: "Requisition Facts"."Job Requisition Open To Offer Extended (Days)". (HY000)
We want to avoid users continue including some fields when creating new reports without affecting existing analysis/report.
Can this be done by changing something else in the repository file? Or is there any other way to do this?
Thanks in advance for any idea/suggestion.Hi,
You mean you restricted "Requisition Facts"."Job Requisition Open To Offer Extended (Days)" in repository for few users,but they are getting nQSError: 27005 when they are openings reports in which this column is already used? Is this what you mean
If so stop your BI Server and go to NQSConfig.INI and change the parameter PROJECT_INACCESSIBLE_COLUMN_AS_NULL which is under security section. By default it is set to NO. Make it YES and restart BI Server.As you restricted that column its showing that error,if you make it show as NULL it will not show any error.
Refer : http://obieeblog.wordpress.com/2009/01/15/obiee-data-security-column-level-security/
Regards,
Srikanth -
Mappings disappeared in OWB...
I have a problem with several mappings that have disappeared from OWB. If I try to export the entire project to an MDL, it will fail. If I try to recreate one of the mappings, it says the object already exists.
Is there any way to recover the mapping? Luckily, we do have backups of the repository, but I'd prefer not to have to rebuild everything from a previous version and merge changes.
I am using OWB 9.2.0.2.8
Thanks.I had the same problem happen to me. I could not discover a logical explanation (I thought I might of mistakenly deleted it, until I saw your post). I did notice that the package existed in the repository schema. I dropped the package from the repository schema (via Toad or SQL PLUS) and recreated the mapping from scratch, painful but it worked. I am concerned that this may happen again if anyone could shed further light to this situation, it would be greatly appreciated.
-
Hello ,
We are facing an issue when checking out a project from Master Repository configured in MUD environment.
Empty presentation folders in subject area's are disappearing when a project is checked out.
I confirmed Master repository has all the empty folders in Presentation Layer Subject Area, but the checked out repository does not have them.
Did anyone encounter this issue? Do you know if there is a patch supporting OBIEE 11.1.1.6.X version.
If "Yes" Can you please share the bug number?
Thanks Again.You most probably haven't set Application Roles in EM for external users.
Users belonging to application roles are only allowed to access OBI.
Check the existing BIConsumer application role, see if you can add external users, and if not, use 'Create Like'. -
MDM Taxonomy attribute values disappearing
Hello -
a problem has been encountered where some of the attributes of the taxonoy table disappear when two taxonomy fields in MDM main table lookup the same taxonomy table.
However, these attribue values still appear in the main table records, they just disappeared from
the "search parameter" area.
Has such a problem ever been encountered? If so - how has it been resolved?
Please let me know
Thank you in advanceHi,
I don't know about any SAP note related to this problem, but you can just refer to Console reference guide and help.sap.com files, there you will find that we cant create a main table field of type taxonomy which refer to same taxonomy table. Its written "A product can belong to at most one leaf-node category." so that can be the reason we can use only one taxonomy table per main table field.
http://help.sap.com/saphelp_mdmgds55/helpdata/EN/8e/9f9c427055c66ae10000000a155106/frameset.htm
See this: Console Reference Guide--> Repository Maintenance -->Designing an MDM Repository -->Taxonomy Lookup Tables
BR,
Alok
Edited by: Alok Sharma on Mar 12, 2008 5:24 PM -
Oracle BI EE repository accessed from Hyperion IR
Hi there.
I'm new to Oracle BI EE. I have imported a new data base (the sample Microsoft Access one that comes with Hyperion) to the physical layer in the Admin tool, created the keys, created the Business Model and Mapping layer and the presentation layer. When I connect to the repository (paint.rpd) with Hyperion Interactive Reporting via ODBC, I can see all the tables (the sample ones already there plus the ones in the database I just added). I can create a datamodel with the tables that came with the paint repository fine, but when I drag in any table from the newly added database they just disappear. No log are produced.
However I can use Answers fine to report off the new database.
Any ideas please?
Many thanks
Bob PentneyI have since found out what to do to make it work. In the presentation layer I replaced the default name of the catalogue (which is the fully qualified path name to the data source) with a simple one word name, eg Sample.
Cheers
Bob -
File System repository error in component monitor
Hi,
I created a file system repository in our portal server which will connect to windows file system and display the folder structure.
I created a File system repository manager with the following properties mentioned below
Prefix (must start with /): /FMICDelaers
Lookup mode: caseless
Root Directory:
fendercorp\FMICDelaers
Repository Services:
Property Search Manager:
Security Manager: W2kSecurityManager
ACL Manager Cache:ca_rsrc_acl
Windows Landscape System: B2B_Windows
I have given full acees to everyone for FMICDealers folder on fendercorp server.
We have created a networkpath called B2B_windows as mentioned below
jCIFS Protocol: yes
Description:
Network Path:
fendercorp\FMICDelaers
Password:xxxxx
User: insidefender\ssayneni
When i am checking the repository in component monitor i am getting the below error
Startup Error: The localroot does not exist: /usr/sap/EPD/JC61/j2ee/cluster/server0/
fendercorp\FMICDealers
Thanks
SushanthHi
A general recommendation would be to use small letters in all ID's regardring network drives, repositories etc. See https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/002fb447-d670-2910-67a5-bfbbf0bb287d for advice on how to optimize performance of KM.
Other than that, you could check the documentation mentioned here:
https://www.sdn.sap.com/irj/sdn/message?messageID=6398301#6398301
It seems as the root directory in your File System Repository Manager is not defined correctly. It should be forward slash instead of backslash.
Go through the settings again and see if the startup error changes or disappears. The startup error indecated that it is a configuration error.
Best regards,
Martin Søgaard
Maybe you are looking for
-
I just purchased a MacBookPro after having a MacBook. I have ILife, IWorks and Office for Mac. How do I get those programs on to my MacBook Pro? I will still use my MacBook at work so I need those programs to remain on it as well.
-
Hello there, Suddenly my Mac has lost all Fire Wire ports Any advice please will be much appreciated Message was edited by: another new convert
-
hi, any idea why when i use the code below i have to enter the text three times before the system recognises it? try { BufferedReader console = new BufferedReader(new InputStreamReader(System.in)); System.out.println("Please type text to convert and
-
Multiple Choices RE: Website Builder Forms
Website Builder at Verizon has forms you can add. On one element, a drop down box of choices you can edit the nature of the drop down. At that area you can check "accept multiple choices" or something close to that. I have that checked but the only c
-
How do you connect the IPod to a radio so I can use the speakers from the radio?
I want to purchase either a shuffle or nano, but I want to use my radio on my boat to connect to the unit. Is this done with wif-fi or is there a connector cable you have to use?