Invalid package body for flows_010500 schema

The following package body will not compile, I ran the utlprp.sql script to recompile as sysdba and they still compile with errors. Is this the schema for version 1.5 and no loner needed if we are using 1.6 htmldb? if so can the flows_010500 be dropped?
wwv_execute_immediate
wwv_flow_audit
wwv_flow_builder
wwv_flow_collection
wwv_flow_disp_page_plugs
wwv_flow_imp_item
wwv_flow_item
wwv_flow_load_data
wwv_flow_query
wwv_flow_svg
wwv_flow_svg
wwv_flow_sw_api
wwv_flow_util
wwv_flow_temp
wwv_flow_utilities
wwv_flow_upgrade
wwv_flow_wizard_api
wwv_render_calendar2
wwv_render_chart2
wwv_render_report3

Janice,
If you have installed 1.6 and upgraded your 1.5 applications, you technically no longer need the FLOWS_010500 schema, and you can drop it.
To be super conservative, you can take an export of it before dropping it, should you find the extremely unlike scenario where you would need to revert back to 1.5.
Thanks,
- Scott -

Similar Messages

VIew of Package body in another schema in EA 3.0

I would like the ability in SQL Developer to view the package body of another schema with the CREATE ANY PRIVILGE.
For instance, in TOAD you can grant access to DBA_SOURCE or SELECT_CATALOG_ROLE and then be able to view another schema's package body.
This is long overdue without having to log into that schema or granting CREATE ANY PRIVILEDGE to user.
This one is really needed

"CREATE ANY PRIVILEGE" is irrelevant to the ability of viewing the source owned by other users.
Please provide exact script for creating a user, which is able to see the code, say in HR schema, via the query
select * from all_source
where owner = 'HR'
and yet missing the nodes in the OtherUsers->Packages->PKG_A->PKG_A Body in the navigator.

Search Package Body for Keywords

I would like to know if anyone has a query to search a package body for a particular word and then return all of the procedure names where that word (or words) are found. I am in the beginning stages of a 3-5 year upgrade/re-write project and just when I think that I have been given all of the requirements "they" come up with something else. Go figure! For instance I might need to find all of the procedures for a package or packages that contain the word product. Manually searching through all of my packages is very time consuming and I'm sure that someone out there has already written a query to do this.
Any help will be greatly appreciated!
Thanks!
Randy

>
I would like to know if anyone has a query to search a package body for a particular word and then return all of the procedure names where that word (or words) are found. I am in the beginning stages of a 3-5 year upgrade/re-write project and just when I think that I have been given all of the requirements "they" come up with something else. Go figure! For instance I might need to find all of the procedures for a package or packages that contain the word product. Manually searching through all of my packages is very time consuming and I'm sure that someone out there has already written a query to do this.
>
A query? No
Would you settle for Oracle supplied functionality that can probably provide all of that cross-reference information for you?
As you can tell from all of the other replies it seems many, if not most, people are not familiar with PL/Scope, which was introduced in version 11.1 (you should always provide your 4 digit Oracle version).
>
PL/Scope is a compiler-driven tool that collects data about identifiers in PL/SQL source code at program-unit compilation time and makes it available in static data dictionary views. The collected data includes information about identifier types, usages (declaration, definition, reference, call, assigment) and the location of each usage in the source code.
PL/Scope enables the development of powerful and effective PL/Scope source code browsers that increase PL/SQL developer productivity by minimizing time spent browsing and understanding source code.
PL/Scope is intended for application developers, and will usually be used in the environment of a development database.
>
See Chapter 8 Using PL/Scope in the Advanced Appication Developer's Guide
http://docs.oracle.com/cd/B28359_01/appdev.111/b28424/adfns_plscope.htm
>
Specifying Identifier Collection
By default, PL/Scope does not collect data for identifiers in the PL/SQL source program. To have PL/Scope collect data for all identifiers in the PL/SQL source program, including identifiers in package bodies, set the PL/SQL compilation parameter PLSCOPE_SETTINGS to 'IDENTIFIERS:ALL'.
>
Without knowing your actual needs or requirements I can't speculate on whether this will give you everything you are looking for.
But don't reinvent the wheel without checking this out first.
Basically just set the compilation parameter and recompile all of the code. Then there will be static dictionary views available with the cross-reference data.
Even if you are not currently using 11g if I were you I would create an 11g sandbox with all of the objects and code (no data needed) just so you could use PL/Scope to get this cross-reference information.

View package body in another schema

I have developers who want to view the code in the package body in another's schema.
I know select text from all_source/ user_source works only for packages in your own schema.
Granting system privelege 'create any procedure' allows the developer to view as well as update priveleges.
As the owner of the objects what grants do I need to give to developers so that they can only view the code.

You can grant select_catalog_role permissions to your developers. This will give your developers select access to all of the V$ views and DBA_% views. Then they can view the dba_source table to view other schema's package code..
Regards,
David

Invalid Package Body

I have a working instance of a commercial product based on an Oracle database. I exported the main schema of the database. I then created a new database with identical tablespaces and users as the original. After importing the .dmp file I found that everything works fine with the exception of a single package body that will not compile due to errors. Unfortunately the code is wrapped so I am unable to view the errors. Considering I have identical tablespace and user characteristics between the two databases, and that I imported the entire main schema owner, would it be correct to assume that the errors in that package must therefore be due to missing objects of other schemas (that were not imported)?

Could be anything really.
- Rights and roles (are all users truely identical)
- Missing/invalid Objects
- Code inside the package (Maybe they check the patchlevel of your database? Or the server name) => Unlikly but possible.
Best thing would be to get support help from the vendor of the commercial product.

Access package body in once schema by another

I have package defined in one schema (A). How can another user (B) access the body of that package logged in as B?

SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE     10.2.0.1.0     Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> connect o/o
Connecte.
SQL> create or replace package p is procedure p; end;
2 /
Package cree.
SQL> create or replace package body p is procedure p is begin null;end; end;
2 /
Corps de package cree.
SQL> grant execute on p to u;
Autorisation de privileges (GRANT) acceptee.
SQL> connect u/u
Connecte.
SQL> select * from all_source where owner='O';
OWNER                      NAME                     TYPE
      LINE
TEXT
O                      P                     PACKAGE
      1
package p is procedure p; end;
O                      P                     PACKAGE BODY
      1
package body p is procedure p is begin null;end; end;
OWNER                      NAME                     TYPE
      LINE
TEXT
SQL>

How to compile HTMLDB_SITE_ADMIN_PRIVS invalid package body?

Hi,
I am trying to grant HTMLDB Administrator privilege to assign the other Oracle default schemas to workspaces by executing the following procedure.
SQL> EXEC HTMLDB_SITE_ADMIN_PRIVS.UNRESTRICT_SCHEMA(p_schema => 'SYSTEM');
However, the package body is corrupted. As the package body is wrapped, I cannot compile it manually.
FLOWS_020000@PROD> ALTER PACKAGE HTMLDB_SITE_ADMIN_PRIVS COMPILE BODY;
Warning: Package Body altered with compilation errors.
FLOWS_020000@pPROD> SHOW ERRORS;
Errors for PACKAGE BODY HTMLDB_SITE_ADMIN_PRIVS:
LINE/COL ERROR
0/0 PLS-00753: malformed or corrupted wrapped unit
I'd greatly appreciate if you can provide any suggestion or advice for me to compile or reload this wrapped package body.
Thanks,
Deborah

Hi,
I am trying to grant HTMLDB Administrator privilege to assign the other Oracle default schemas to workspaces by executing the following procedure.
SQL> EXEC HTMLDB_SITE_ADMIN_PRIVS.UNRESTRICT_SCHEMA(p_schema => 'SYSTEM');
However, the package body is corrupted. As the package body is wrapped, I cannot compile it manually.
FLOWS_020000@PROD> ALTER PACKAGE HTMLDB_SITE_ADMIN_PRIVS COMPILE BODY;
Warning: Package Body altered with compilation errors.
FLOWS_020000@pPROD> SHOW ERRORS;
Errors for PACKAGE BODY HTMLDB_SITE_ADMIN_PRIVS:
LINE/COL ERROR
0/0 PLS-00753: malformed or corrupted wrapped unit
I'd greatly appreciate if you can provide any suggestion or advice for me to compile or reload this wrapped package body.
Thanks,
Deborah

Version 3.0.04 (04.34) Quick Outline not displaying for Package Body

All,
I am using the latest release of SQL Developer (Version 3.0.04 Build MAIN-04.34)
When I try and do a quick outline on one of the packages the package body node + sign disappears and the quick outline is empty apart from the package body name.
I have checked I have no < or > in text or anonymous pl/sql blocks within procedures as per previous posts.
The package body is over 6000 lines long but a package body which is 8000 lines displays the outline correctly.
Has anyone else experienced this behaviour ?
The package body has not changed and the quick outline worked in v2 versions of SQL Developer.
Any ideas ?
Cheers
Chris

Hi, I can confirm I am having the same problem as ChrisR, I have the same SQL Developer version.
I found out that the parser have probably problems with declared functions and procedures at the beginning of the package body...
Anyway, when I was searching what's going on, I found somewhere on the internet that this bug was reported long time ago in version 2.xx and it should be fixed in version 3.
Here is the link
Package Body Tree not always showing
So I went here:
http://www.oracleimg.com/technetwork/developer-tools/sql-developer/sqldev30-bugsfixed-349809.html
to check if the bug is really fixed and the only similar issue I found was this bug:
10082343 SQL Developer not displaying package body for another user
I visited the "Known issues" site here
http://www.oracleimg.com/technetwork/developer-tools/sql-developer/sqldev30-knownissues-349810.html
to check if it's not listed there and...nothing
So I searched SQL Developer forum and found this topic...
Come on... when this is known problem, why it is not listed in Known issues section???
This way you make users search all the developer settings, all over the internet and spend hours before they find this is know problem long time...

Package Body SYS.DBMSOBJG - status invalid

I have created two database version 8.1.7.0.0 on WindowsNT 4.0 SP5.
One package body DBMSOBJG under SYS is invalid and the status remains same even after compilation. The source is wrapped. How can i turn it to valid. Till time i have not experienced any problem with database but don't know the future implecations because of this invalid package body.
Regards

Pl detail how you upgraded to EE version
https://docs.oracle.com/cd/E11882_01/server.112/e23633/intro.htm#UPGRD12355

Help required in compilation of package body.....

Hi ..
While taking the export i encounter the error message..
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 26:
PLS-00201: identifier 'XDB.DBMS_XDBUTIL_INT' must be declared
ORA-06550: line 1, column 14:
PL/SQL: Statement ignored
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 26:
PLS-00201: identifier 'XDB.DBMS_XDBUTIL_INT' must be declared
ORA-06550: line 1, column 14:
PL/SQL: Statement ignored
EXP-00000: Export terminated unsuccessfully..
SELECT status,object_id,object_type,owner,object_name
FROM dba_objects
WHERE object_name = 'DBMS_XDBUTIL_INT';
gives the output as...
status object type owner object_name
valid synonym public DBMS_XDBUTIL_INT
valid package xdb DBMS_XDBUTIL_INT
invalid package body xdb DBMS_XDBUTIL_INT
when i try to compile the invalid object...
SQL> alter package XDB.DBMS_XDBUTIL_INT COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> sho err
Errors for PACKAGE BODY XDB.DBMS_XDBUTIL_INT:
LINE/COL ERROR
61/7 PL/SQL: Statement ignored
61/17 PLS-00306: wrong number or types of arguments in call to
'IS_HIERARCHY_ENABLED_INTERNAL'
74/7 PL/SQL: Statement ignored
74/29 PLS-00302: component 'GENERATE_TRGNM' must be declared
108/9 PL/SQL: Statement ignored
108/37 PLS-00302: component 'TRUNCATE_NAME' must be declared
123/7 PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
123/7 PL/SQL: Statement ignored
135/9 PL/SQL: Statement ignored
LINE/COL ERROR
135/37 PLS-00302: component 'TRUNCATE_NAME' must be declared
153/9 PL/SQL: Statement ignored
153/33 PLS-00302: component 'TRUNCATE_NAME' must be declared
168/7 PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
168/7 PL/SQL: Statement ignored
181/9 PL/SQL: Statement ignored
181/33 PLS-00302: component 'TRUNCATE_NAME' must be declared
Since the code is wrapped .. i cant do anything.. needs ur help.
sorry for explaining in such a detail...
Message was edited by:
437022

Hi,
In side the Package Body,
a) invalid arguments for IS_HIERARCHY_ENABLED_INTERNAL
b) invalid components GENERATE_TRGNM, etc.
First, you need to correct the above errors and then
try to compile the Package Body
Regards,
Sailaja

Issue with viewing Package Body in SQL Developer 2.1 EA1

I was able to view the package body from different schemas after I log in with user account in SQL Developer 1.5.5.
But with SQL Developer 2.1 EA1, I could view only spec and I can see the package body only if I log in with DBO account.
Is there any setting that needs to be configured to be able to view the package body?
Thanks!

Thanks for replying my message.
It's Oracle 9i.
What I meant 'spec' is you can see only the headers you defined in spec. You can expend the package and be able to see the all functions and procedures but you won't be able to see the '%packagename% Body' where all the detail code were written.
As I mentioned in my previous post, with SQL Developer 1.5.5 version, you can see spec and package body if you expend the package.

Can't compile package body

hello. i ran in to little issue today. After patch 13839550 was applied to one of our test enviroments, we get one invalid package body. but when i try to compile it shows warrning!
SQL> alter package APPS.AP_ACCTG_DATA_FIX_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL>
SQL> show err
Errors for PACKAGE BODY APPS.AP_ACCTG_DATA_FIX_PKG:
LINE/COL ERROR
3899/3 PL/SQL: SQL Statement ignored
3899/3 PLS-00394: wrong number of values in the INTO list of a FETCH
statement
Could you please explain what should i do?
Database - 11.2.0
eBS - 12.1
Linux x86
Thx

i dont understand how can ichange something here?In this case, you can't.
If this is one of the standard packages built into an Oracle Apps database, you need to log a tar/sr with Oracle support. (which will probably result in more patches)

Package owner - invalid packages

Hello guys,
I have this problem: I have two DB schemes A and B. I modified the code in both schemes. After compilation, many packages were invalidated. So I compiled all invalid packages, no compilation errors, everything ok.
Now if I run this query in scheme A:
SELECT *
FROM ALL_OBJECTS
WHERE OBJECT_TYPE IN ('PACKAGE', 'PACKAGE BODY')
AND STATUS = 'INVALID';I get two records.
The first one shows an invalid package where owner is scheme C - this is ok, because in scheme C is really such invalid package which has granted execute to scheme A.
The second one shows an invalid package body, where owner is scheme A. But in scheme A, there is no such package. The "invalid" package is in fact in scheme B, it is in fact not invalid and it has no grants at all. So scheme A has no access to that package at all.
Recompilation of this package in scheme B has no impact on the result. Why is the package marked as invalid and why is scheme A assigned as an owner???
Now I run exactly same query in scheme B and get one record.
One package is marked as invalid where owner is scheme B. However this package is in scheme A and scheme A is the owner of this package. Again the package is not invalid and recompilation of that package has no impact... In this case the package has granted execute to scheme B, so scheme B has the access to this package.
Can anyone help me with this?
Thanks, Dan

I found the problem...
After I did those changes to that packages, I first compiled the bodies to wrong schemes. So the bodies were created without specifications. I didn't see those packages because SQL Developer doesn't display them in such case...
So I droped them now.

Grant command to view package body

I sent a request for the DBA's to grant me rights to the package body but I only see the spec with the grant execute command.
Here is the command I just sent:
grant create any procedure to DEVELOPER1;
But the DBA changed my grant command to:
grant create procedure to DEVELOPER1;
But I still cannot see the package body. This is on a test environment.
Would the "create any procedure" command help me see the package body of different schema owners package bodies?
Or is there another grant command to see different schema package bodies?

primefsu wrote:
My dba say that you cannot use debug in this grant because session belongs right after debug.I have no clue what your dba is talking about. Anyway:
SQL> create or replace
2    package pkg1
3      is
4        procedure p1;
5 end;
6 /
Package created.
SQL> create or replace
2    package body pkg1
3      is
4        procedure p1
5          is
6          begin
7              null;
8        end;
9 end;
10 /
Package body created.
SQL> grant execute on pkg1 to u1
2 /
Grant succeeded.
SQL> connect u1@orcl
Enter password: **
Connected.
SQL> exec scott.pkg1.p1;
PL/SQL procedure successfully completed.
SQL> select text
2    from all_source
3    where owner = 'SCOTT'
4      and name = 'PKG1'
5      and type = 'PACKAGE BODY'
6    order by line
7 /
no rows selected
SQL> connect scott@orcl
Enter password: *****
Connected.
SQL> grant debug on pkg1 to u1
2 /
Grant succeeded.
SQL> connect u1@orcl
Enter password: **
Connected.
SQL> select text
2    from all_source
3    where owner = 'SCOTT'
4      and name = 'PKG1'
5      and type = 'PACKAGE BODY'
6    order by line
7 /
TEXT
package body pkg1
    is
      procedure p1
        is
        begin
            null;
      end;
end;
8 rows selected.
SQL> As you can see, package body became visible to user U1 as soon as user U1 was granted DEBUG on package.
SY.

DBMS_METADATA Package Body won't compile

I get a PLS-00103 error when attempting to complile the package body for SYS.DBMS_METADATA. The body hasn't been modified so I'm not sure where to look.

Or,
Does anyone know where in a script I can find the line that created this package and body in the first place?

Invalid package body for flows_010500 schema

Similar Messages

Maybe you are looking for