Clarity

  • 1.  Actuate errors when deployed

    Posted Apr 24, 2009 10:49 AM
    Hi,I have a report that compiles and runs fine from eRDPro. But when deployed on actuate, it fails on actuate (http://server_name:8900/acadmin) with error 'Database login failed (ORA-01821: date format not recognized)".   We have Actuate 7. Any ideas?   Thanks lot!!  -Ashutosh


  • 2.  Re: Actuate errors when deployed

     
    Posted Apr 27, 2009 10:01 AM
    Hi Ashutosh,  I checked with someone who knows Actuate setup fairly well and below is his reply.   Please note Actuate 9 is the supported version at this time.  Regards,Chris   Not certain but looks like a database connection issue.   Have them test the connection, using ping and tnsping between the Actuate reports server box and the Clarity database.   The same credentials used to tnsping should be reflected in the NSA Reporting tab.


  • 3.  Re: Actuate errors when deployed

    Posted May 01, 2009 12:35 PM
    Thank you, Chris for your inputs.The issue has changed.   We have not changed anything yet.  Now when the report is run on actuate itself ( http:// :8900/acadmin ) it gives an error saying  "Failed to Execute the Report!  Error Description: Status No: 1 :Basic Error: 1011Module: afc\db.basLine: 193  Database Error3: Database login failed.1821: ORA-1821: date format not recognized"    Any inputs you have would be greatly helpful.    Thanks and Regards,Ashutosh


  • 4.  Re: Actuate errors when deployed
    Best Answer

     
    Posted May 01, 2009 12:55 PM
    Hi Ashutosh,  The only other suggestion is possibly KB article # 7935.   Beyond this you should log an issue with Support unless any other users have an idea.   Please note since Actuate 9 is the only supported version you may need to be on that version before Support will assist.  Regards,Chris   Document ID :     TEC439367 [left][left] Tech Document [left] Title:     RPT-0002: This report is not configured properly. Error after the upgrade to 7.5.3 fp03 from 6.1.5 (Niku KB ID: 7935) [left] SYMPTOMS ========== Immediate Reports run from Actuate console or from Clarity menu system fail to run. Error after upgrade to 7.5.3 FP03 from 6.1.5 RPT-0002: This report is not configured properly. The report /CMN/companies.rox did not execute properly. Error from server is Status No: 1 : Basic Error: 1002 Module: afc\report.bas Line: 1552 User error. Any Scheduled reports and jobs run without error. CAUSE ====== Basic root cause was that the reports are using libraries that are trying to force the report to use the old Oracle 8i interface when in reality it should be using Oracle 9i interface. WORKAROUND ============== STATUS/RESOLUTION ===================== To resolve this, we made the following change to our SUN/Solaris system: Go to $ACSERVER_HOME/lib Perform the following move commands: mv libacorcl7.so libacorcl7.so.orig mv libacorcl80.so libacorcl80.so.orig mv libacorcl81.so libacorcl81.so.orig Then duplicate the 9i file to replace the original files you just renamed: cp libacorcl90.so libacorcl7.so cp libacorcl90.so libacorcl80.so cp libacorcl90.so libacorcl81.so Stop and restart reporting. niku stop reports niku start reports And that should work. Another option that we do not use would be to fix the code in the NikuReportControls.rol file. The file looks like this today: Function Connect( ) As Boolean HostString = NikuSequential::Host_string UserName = NikuSequential::User_name Password = NikuSequential::Pass_word If NikuSequential::dbVersion = "9" Then DBInterface = "acorcl90" Else DBInterface = "acorcl81" End If Connect = Super::Connect( ) End Function The fix would look like this (theoretically - this has not been tested!): Function Connect( ) As Boolean HostString = NikuSequential::Host_string UserName = NikuSequential::User_name Password = NikuSequential::Pass_word DBInterface = "acorcl90" Connect = Super::Connect( ) End Function MORE INFORMATION ================== Note that for Windows operating systems: the "mv" command should be replaced with 'rename' and the "cp" command should be replaced with 'copy'. Keywords ======== Actuate immediate RPT-0002[left][left][left][left][left][left]


  • 5.  Re: Actuate errors when deployed

     
    Posted Jun 01, 2009 08:15 AM
    Adding a note to push this forward after board consolidation.