Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors appears in the App Builder (import): Build Status must be specified. Parse As Schema must be specified. File is not a valid Oracle APEX application export file. #10

Closed
fisal77 opened this issue Nov 4, 2023 · 10 comments
Assignees
Labels
APEX bug Issue on APEX

Comments

@fisal77
Copy link

fisal77 commented Nov 4, 2023

In the App Builder when I send files (blog-administration-latest.sql) & (blog-public-pages-latest.sql) to import the below errors appears:

3 errors have occurred
Build Status must be specified.
Parse As Schema must be specified.
File is not a valid Oracle APEX application export file.

Please help me.

image
@jariolaine jariolaine self-assigned this Nov 4, 2023
@jariolaine
Copy link
Owner

I'm not yet able to find what causes this because import works when running e.g. from SQLcl.

Workaround is use e.g. SQLcl to install applications.
Here is example how import applications:

set serveroutput on size unlimited;

-- Import blog admin application
begin
  apex_application_install.generate_offset;
  apex_application_install.set_auto_install_sup_obj( p_auto_install_sup_obj => true );
  -- Set your workspace name
  apex_application_install.set_workspace( '<WORKSPACE_NAME>' );
  -- Set your schema name
  apex_application_install.set_schema( '<SCHEMA_NAME>' );
  -- Set application id
  apex_application_install.set_application_id( 402 );
end;
/
@blog-administration-latest.sql;

-- Import blog public application
begin
  apex_application_install.generate_offset;
  apex_application_install.set_auto_install_sup_obj( p_auto_install_sup_obj => true );
  -- Set your workspace name
  apex_application_install.set_workspace( '<WORKSPACE_NAME>' );
  -- Set your schema name
  apex_application_install.set_schema( '<SCHEMA_NAME>' );
  -- Set application id
  apex_application_install.set_application_id( 401 );
end;
/
@blog-public-pages-latest.sql;

-- Query errors
select *
from user_errors
;

@jariolaine
Copy link
Owner

Have you connected right database and user? Errors indicate that database where you have connected doesn't have APEX installed.
Also check that user you use is assigned to APEX workspace where you going to import applications.

@fisal77
Copy link
Author

fisal77 commented Nov 5, 2023

Hi @jariolaine,
Thank you for your reply.
I follows your instructions as above but appears this error:

Error report -
ORA-06550: line 2, column 3:
PLS-00201: identifier 'APEX_APPLICATION_INSTALL.GENERATE_OFFSET' must be declared
ORA-06550: line 2, column 3:
PL/SQL: Statement ignored
ORA-06550: line 3, column 3:
PLS-00201: identifier 'APEX_APPLICATION_INSTALL.SET_AUTO_INSTALL_SUP_OBJ' must be declared
ORA-06550: line 3, column 3:
PL/SQL: Statement ignored
ORA-06550: line 5, column 3:
PLS-00201: identifier 'APEX_APPLICATION_INSTALL.SET_WORKSPACE' must be declared
ORA-06550: line 5, column 3:
PL/SQL: Statement ignored
ORA-06550: line 7, column 3:
PLS-00201: identifier 'APEX_APPLICATION_INSTALL.SET_SCHEMA' must be declared
ORA-06550: line 7, column 3:
PL/SQL: Statement ignored
ORA-06550: line 9, column 3:
PLS-00201: identifier 'APEX_APPLICATION_INSTALL.SET_APPLICATION_ID' must be declaredORA-06550: line 9, column 3:
PL/SQL: Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause: Usually a PL/SQL compilation error.
*Action: Refer to the following PL/SQL messages for more
information about the error.

More Details :
https://docs.oracle.com/error-help/db/ora-06550/
https://docs.oracle.com/error-help/db/pls-00201/
--application/set_environment

@jariolaine jariolaine added the APEX bug Issue on APEX label Nov 5, 2023
@jariolaine
Copy link
Owner

jariolaine commented Nov 5, 2023

It seems splitted export import works.
You can download whole repository.
Go to repository home page and click green "Code" button. Click "Download ZIP".
image

Extract ZIP and then go extracted folder -> APEX.
Zip folder blog_administration and create another Zip from folder blog_public_pages.
You can now import those created Zip files using APEX builder. Remember import first Zip containing blog_administration,

@jariolaine
Copy link
Owner

jariolaine commented Nov 5, 2023

I managed identify problem. It seems when including Copyright Banner application export is corrupted. This is APEX bug.

jariolaine added a commit that referenced this issue Nov 5, 2023
@jariolaine
Copy link
Owner

Issue is fixed in latest version.

@fisal77
Copy link
Author

fisal77 commented Nov 5, 2023

It seems splitted export import works. You can download whole repository. Go to repository home page and click green "Code" button. Click "Download ZIP". image

Extract ZIP and then go extracted folder -> APEX. Zip folder blog_administration and create another Zip from folder blog_public_pages. You can now import those created Zip files using APEX builder. Remember import first Zip containing blog_administration,

Thank you for your help. I've follow the above instructions but this error appears:

Application parsing schema must have role CTXAPP or execute privilege to package CTX_DDL.

image

Could you please help how I can give Application parsing schema role CTXAPP ?... I'm still new in Oracle DBA :( ....

@jariolaine
Copy link
Owner

Connect to DB as SYS and grant CTXAPP role to schema associated to your APEX workspace.

grant ctxapp to <schema name>;

@fisal77
Copy link
Author

fisal77 commented Nov 7, 2023

Thank you. my 'grant CTXAPP' problem solved. but appears new issue in blog_administration only & it's running as below screenshot:

image

Note: blog_public_pages was succussed in installation steps...

Please help me.

@jariolaine
Copy link
Owner

jariolaine commented Nov 8, 2023

Unfortunately you are hitting another APEX bug 35410651 that is fixed in latest APEX 23.1 patch set bundle 35283657. You should apply that that patch before installing applications.
Or workaround is run supporting objects database_objects.sql scripts using e.g. SQLcl when connected to application parsing schema.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APEX bug Issue on APEX
Projects
None yet
Development

No branches or pull requests

2 participants