After migration to 1.9 a below error occures in LIVE env.:

ERROR : An error occured while initializating Panel 22845. 
ORA-06512: na "FORMSPIDER.BDF_SUPPORT", line 595
ORA-06512: na "FORMSPIDER.BDF_DBOBJECTACCESS_MNG", line 2408
ORA-06512: na "FORMSPIDER.BDF_DBOBJECTACCESS_MNG", line 2511
ORA-06512: na "FORMSPIDER.BDF_DBOBJECTACCESS_MNG", line 2501
ORA-06512: na "FORMSPIDER.BDF_DBOBJECTACCESS_MNG", line 87
ORA-06512: na "FORMSPIDER.BDF_PANELDTL_MNG", line 416
ORA-06512: na "FORMSPIDER.P_22840", line 410
ORA-06512: na "FORMSPIDER.P_22840", line 510
ORA-06512: na "FORMSPIDER.P_22838", line 105
ORA-06512: na "FORMSPIDER.P_22838", line 179
ORA-06512: na "FORMSPIDER.P_22845", line 80
ORA-06512: na "FORMSPIDER.P_22845", line 154
ORA-06512: na line 1
ORA-06512: na "FORMSPIDER.BDF_PANEL_MNG", line 125

ERROR : in_panel_oid :22845(init) errmsg : ORA-06502: PL/SQL: číselná nebo hodnotová chyba: hodnota klíče tabulky indexu je NULL

Please suggest what could be wrong please.

asked 27 Sep '15, 03:26

Tomeo's gravatar image

Tomeo
162249
accept rate: 3%


Hi Tomas,

In your email, you mentioned that you ran your Formspider 1.8 developer license script in your Formspider 1.9 installation. I don't know if this is the reason of your problem but I know that Formspider 1.9 has a new license script and it may cause problems to run the 1.8 license script in 1.9.

I recommend you to test FS 1.9 in a test environment first and then deploy to production only if you see no problems in test.

Kind Regards,
Yalim

link

answered 28 Sep '15, 04:55

Yalim's gravatar image

Yalim ♦♦
2.8k5
accept rate: 22%

Hi Yalim,

we upgraded to 1.9, but a developer license from 1.8 was not run there. I don't have a license script for 1.9 yet.

In test env everything is OK, so have no idea why application has problem in LIVE env. Is above error linked to licensing?

So far I had to downgrade back to 1.8.1 version in LIVE.

Tomas

link

answered 28 Sep '15, 05:52

Tomeo's gravatar image

Tomeo
162249
accept rate: 3%

Hi Tomas,

If you did not run the FS 1.8 license script, then the error is not related. I thought you did run it. I probably misunderstood your email.

Kind Regards,
Yalim

(28 Sep '15, 07:19) Yalim Gerger ♦♦

Hello folks,

any idea how to track what's wrong? It's pointing to formspider's packages, so have no clue what's wrong.

Regards, Tomas

link

answered 29 Sep '15, 10:46

Tomeo's gravatar image

Tomeo
162249
accept rate: 3%

For importing application into LIVE and, we use an EXPORT script from DEV env and then IMPORT script into LIVE db. Could something change with upgrade 1.9, so export/import scripts does not work correctly?

Please see my scripts below:

1.Application export, from dev env.

declare
  cursor c is
     select NAME_TX, DEV.API_FS_APP_VERSION.get_version_ag_doprava version
       from T_BDF_APPLICATION
       where NAME_TX = 'AG Doprava';

  v_xml                 xmltype;
  v_applicationName_tx  varchar2(255);
  v_directoryName_tx    varchar2(255) := 'FORMSPIDER_DIR';
  ------------------------------------------------------------------------------
  procedure saveCLOBtoFile(in_directoryName_tx varchar2, in_filename_tx varchar2, in_application_xml xmltype)
  is
  begin
    dbms_xslprocessor.clob2file(xmltype.extract(in_application_xml, '/*').getClobVal(), in_directoryName_tx, in_filename_tx);
  end;
  ------------------------------------------------------------------------------
BEGIN
  for x in c loop
    v_applicationName_tx := x.NAME_TX;
    v_xml := api_application.export(v_applicationName_tx);
    saveCLOBtoFile(v_directoryName_tx, v_applicationName_tx||'-'||x.version||'.xml',v_xml);
  end loop;
END;
/

exit;

2.Import exported application into LIVE db.

   declare
      v_oracleDirectory_tx varchar2(255) := 'FORMSPIDER_DIR'; 
      v_applicationName_tx varchar2(255) := 'AG Doprava';
      v_xmlFileName_tx varchar2(255) := v_applicationName_tx||'-'||DEV.API_FS_APP_VERSION.get_version_ag_doprava||'.xml';
      v_cl clob;

      v_file bfile;
      v_destoffset number:=1;
      v_srcoffset number:=1;
      v_warning number:=0;
      v_context number:=0;

      v_objectRecord_tt bdf_etl.tt_importObjects;

    begin

      bdf_application_api.applicationdelete(in_application_oid=>bdf_application_qry.getid(v_applicationName_tx), in_cascade_yn=>'Y');

      dbms_lob.createtemporary(v_cl,true);
      v_file  := BFILENAME(v_oracleDirectory_tx, v_xmlFileName_tx);

      dbms_lob.open(v_file, dbms_lob.lob_readonly);

      dbms_lob.loadclobfromfile(v_cl, v_file, DBMS_LOB.LOBMAXSIZE , v_destoffset, v_srcoffset, nls_charset_id('AL32UTF8'), v_context, v_warning);

      dbms_lob.close(v_file);

      bdf_etl.load(in_bdf_xml=>xmltype(v_cl),
                   in_importOption_cd =>'AsNewApplication',           -- leave it as it is
                   in_projectOption_cd=>bdf_constant_etl.etlcreateOrReplace,
                   in_applicationOption_cd=>bdf_constant_etl.etlcreateOrReplace,
                   in_importObjects_tt=>v_objectRecord_tt);

      commit;
    end;
    /

    exit;

Both scripts run fine, but when application is run in dev env, above formspider error occurs.

link

answered 04 Oct '15, 04:26

Tomeo's gravatar image

Tomeo
162249
accept rate: 3%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×43

Asked: 27 Sep '15, 03:26

Seen: 1,194 times

Last updated: 04 Oct '15, 04:26


© Copyright Gerger 2017