Apex 3.1.2.00.02 creates invalid export file (that gives ORA-20001 error)

Question

Hi
I want to let you know, that sometimes APEX 3.1.2.00.0 creates invalid export file.
Older apex 3.0 created correct file.
For example: our application has page button, where "Optional URL Redirect" is:
Page: &APP_PAGE_ID.
Request: FLOW_XMLP_OUTPUT_R11531800061044170_et
If we export application into file f110.sql and try to import it to the same workspace on the same server, we get error:
{color:#0000ff}ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 28, column 111: PLS-00103: Encountered the symbol "_" when expecting one of the following: ) , * & | = - + < / > at in is mod remainder not rem => .. <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_ LIKE4_ LIKEC_ as between from using || multiset member SUBMULTISET_ The symbol &a
{color}In exported f110.sql file the invalid section is:
{color:#0000ff}wwv_flow_api.create_page_branch(
p_id=>11762805016890347 + wwv_flow_api.g_id_offset,
p_flow_id=> wwv_flow.g_flow_id,
p_flow_step_id=> 4,
p_branch_action=> 'f?p=&APP_ID.:&APP_PAGE_ID.:&SESSION.:FLOW_XMLP_OUTPUT_R'||to_char({color}{color:#0000ff}{color:#ff0000}*10255206661122183_et*{color}+wwv_flow_api.g_id_offset)||':&DEBUG.:::',
p_branch_point=> 'AFTER_PROCESSING',
p_branch_type=> 'REDIRECT_URL',
p_branch_when_button_id=>11761415275883875+ wwv_flow_api.g_id_offset,
p_branch_sequence=> 10,
p_branch_comment=> 'Created 20-JUUNI-2008 12:05 by XXXX');{color}
If we exported the same application in apex 3.0, this section was correct:
{color:#0000ff}wwv_flow_api.create_page_branch(
p_id=>11762805016890347 + wwv_flow_api.g_id_offset,
p_flow_id=> wwv_flow.g_flow_id,
p_flow_step_id=> 4,
p_branch_action=> 'f?p=&APP_ID.:&APP_PAGE_ID.:&SESSION.:FLOW_XMLP_OUTPUT_R*10255206661122183_et*:&DEBUG.:::',
p_branch_point=> 'AFTER_PROCESSING',
p_branch_type=> 'REDIRECT_URL',
p_branch_when_button_id=>11761415275883875+ wwv_flow_api.g_id_offset,
p_branch_sequence=> 10,
p_branch_comment=> 'Created 20-JUUNI-2008 12:05 by XXXX');{color}
Best Regards,
Tõnu

Answer 1

Thanks for pointing that out. We'll fix it. It does appear though, that in 3.0, the offset would not be added to the number part of the request value, so if you installed the application as a different application ID or into a different workspace, the request would have failed.
Scott