Architecting, installing and maintaining your SAS environment

Oracle Content server Issue

Reply
Contributor
Posts: 26

Oracle Content server Issue

Hi ,

SAS 9.2 with Oracle 11.

we have a scenarios where we have moved SAS Metadata/ compute and mid tier from one physical server to another ( config and binaries ) movement . we are able to

make everything work expect the content server , currently. which in the old environment used Oracle Database as Content server.

when i login to content server URL http://serverSmiley Tongueort/SASContentServer/dircontents.jsp  , i see sasfolders and sasdav folder with all the reports from the old

environment , is it showing form the indexes on the file system or retrieving the data from Oracle content server ?

1) Now , my understanding is when  when a user / folder is created in SAS SMC it should make a corresponding folder in the content server database in which Table can

i check this ?

2)we are also not able to open an existing reports which are currently  in Content server ( Web report ) , it gives back end service has error.

3) i saw in one of the notes we can check only the size of the table growing , is there any specific table we can check.when i see database i see

SAS_SCS_DEFAULT_BINVAL , SAS_SCS_DEFAULT_BUNDLE table have lot of rows compared to other tables.

Error when we are trying to save the report , message in  WRS log is as below . also we have changed the URL's to access the webreport / stored process

2014-09-02 11:49:13,473 [WebContainer : 6] ERROR [e317e7fdee947c95:715de5e1:1481d7f5434:-56cpgunti] com.sas.apps.citation.model.repository.adapter.PathHelper -

Unexpected error accessing this user's personal application folder.

Root Cause:   com.sas.report.repository.ContentException: '400:Bad Request' error while accessing 'https://XXXXX . XXX . XXX :443/SASContentServer/repository/

default/sasfolders/Users/<<User>>/Application Data'

       at com.sas.report.repository.ContentProviderDAV.checkStatus(ContentProviderDAV.java:97)

       at com.sas.report.repository.ContentProviderDAV.initialize(ContentProviderDAV.java:208)

       at com.sas.report.repository.ContentProviderDAV.<init>(ContentProviderDAV.java:148)

       at com.sas.report.repository.ContentFactory.initialize(ContentFactory.java:52)

       at com.sas.report.repository.ContentFactory.create(ContentFactory.java:21)

       at com.sas.report.repository.OMRDirectory.getContent(OMRDirectory.java:2937)

       at com.sas.report.repository.OMRDirectory.createDirectory(OMRDirectory.java:255)

       at com.sas.report.repository.OMRDirectory.ensurePath_p(OMRDirectory.java:2822)

       at com.sas.report.repository.OMRDirectory.ensurePath_p(OMRDirectory.java:2826)

       at com.sas.report.repository.OMRDirectory.ensurePath_p(OMRDirectory.java:2826)

       at com.sas.report.repository.OMRDirectory.ensurePath(OMRDirectory.java:2764)

       at com.sas.report.repository.OMRRepository.ensurePath(OMRRepository.java:602)

       at com.sas.apps.citation.model.repository.adapter.RRBasedCitationRepository.getDirectory(RRBasedCitationRepository.java:1128)

       at com.sas.apps.citation.model.repository.adapter.PathHelper.getUsersWRSProductDir(PathHelper.java:486)

       at com.sas.apps.citation.model.user.history.HistoryStoreMetadataImpl.getHistFileUrl(HistoryStoreMetadataImpl.java:308)

       at com.sas.apps.citation.model.user.history.HistoryStoreMetadataCachingImpl.loadCacheFromRepos(HistoryStoreMetadataCachingImpl.java:113)

       at com.sas.apps.citation.model.user.history.HistoryStoreMetadataCachingImpl.getInputStream(HistoryStoreMetadataCachingImpl.java:63)

       at com.sas.apps.citation.model.user.history.HistoryStoreStreamBase.load(HistoryStoreStreamBase.java:76)

       at com.sas.apps.citation.model.user.history.UserHistoryManager.load(UserHistoryManager.java:140)

       at com.sas.apps.citation.model.user.SessionScopeManager.noteLogonHasCompleted(SessionScopeManager.java:2521)

       at com.sas.apps.citation.model.user.CitationLogonManager.notifySessionManagerOfLogon(CitationLogonManager.java:628)

       at com.sas.apps.citation.model.user.CitationLogonManager.logonUserNow(CitationLogonManager.java:386)

       at com.sas.apps.citation.model.user.CitationLogonManager.logonUser(CitationLogonManager.java:300)

       at com.sas.apps.citation.controller.action.LogonAction._attemptLogon(LogonAction.java:347)

       at com.sas.apps.citation.controller.action.LogonAction.doPerform(LogonAction.java:170)

       at com.sas.apps.citation.controller.action.CitationAction._execute(CitationAction.java:191)

       at com.sas.apps.citation.controller.action.CitationAction.execute(CitationAction.java:166)

       at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)

       [ 65 lines suppressed ]

Which Caused: com.sas.apps.citation.model.repository.adapter.CitationRepositoryException: Could not get raw directory: SBIP://METASERVER/Users/<<User>>/

Application Data/SAS Web Report Studio(Folder)(Reason : Operation Failed) [ com.sas.report.repository.RepositoryException: '400:Bad Request' error while accessing

'https://XXXX.XXX.XXXX.XXX:443/SASContentServer/repository/default/sasfolders/Users/<<User>>/Application Data' [ com.sas.report.repository.ContentException:

'400:Bad Request' error while accessing 'https://XXXX.XXX.XXXX.XXX:443/SASContentServer/repository/default/sasfolders/Users/<<User>>/Application Data' ]  ]

can anybody help or having similar experience ? do we need to change the configuration in database server name in any files ?  we are using IBM Websphere as web application and configured database there and it working finr.

THanks

keds

Contributor
Posts: 26

Re: Oracle Content server Issue

dpage, Jaap Karman ,Mark@sas .. any inputs ?


Trusted Advisor
Posts: 3,212

Re: Oracle Content server Issue

kedar shankargouda your post is very dedicated in a step of a migration.  Missing is the context of all what is done and happened before.
As HCL is a big service provider the reason for this migration can be anything of moving around in datacenters or an initial outsourcing contract.


Migrating to another machine is possible with SAS but poses several questions as there are everywhere DNS-names ports users passwords being defined in this complicated environment. Building up an new machine con be done by:

1/ full image machine copy. Afterwards changing all the names to reflect a new naming convention.

    This requires though knowledge and testing/validating the SAS environment as proces.

2/ build a new machine environment and than migrate all content. 

   The build of new machine is doing the whole installation and configuration proces.

   For migration of the content there is a tool. SMU SAS(R) 9.3 Intelligence Platform: Migration Guide     

It seems to me you have chosen option 1/ for some reason. With option 2/ an upgrade to a newer SAS version would make more sense (eg 9.4). For licensing costs this is not an issue. SAS claims you can upgrade at no license cost.

Assuming you have gone for option 1 and did make a copy of the image.

The first test would be of this image is complete functioning. As there a duplicate machinenames dns-names this is only possible as a DR approach in an isolated network.

(did you?)

All users/passwords keeping the same is preventing a lot of trouble, they are hardcoded everywhere . Do you have to change those also than this is a lot of work to find those places and verify changes are effective.

Than changing all the dns-names, there are also a lot of locations:

- the metadata is the most visible part.   After this restarting and verifying WS SP are working on the correct server 

- all configuration files. These are used at initial connections. The objectspawner need to know wicht metadatasever to connect. That is in a config file not in metadata.

- The java container. This one can have cached own versions. Did you copy that as image, there can be a redeploy necessary after changes.

      

Now your error message. It is WRS a part of an JAVA-container application (websphere). 

It is telling only the contentserver is not reachable. It does not tell you whether the dns-name is wrong or the user/password is wrong, or ?

Nice... (no not nice)
I am wondering how the backup restore of data in the metadata is agreed.

Normal expectation is restoring of one artifact of eg yesterday may be asked and being serviced.  

---->-- ja karman --<-----
Ask a Question
Discussion stats
  • 2 replies
  • 653 views
  • 0 likes
  • 2 in conversation