OWB View validation??

OWB View validation??
We are using OWB repository 10.2.0.2.0 and OWB client 10.2.0.2.8. The Oracle version is 10 G (10.2.0.2.0). OWB is installed on Sun 64 bit server.
We created view in OWB mapping. The validation was successful. As we deploy the view, we are getting errors such as Table/view does not exist, numeric errors etc.
Why does not view validation pick upuch errors?
Did any one in this forum face such issues?
Any idea?
Thanks in advance.
RI

Hello RI,
Creating views as a target in a mapping is only available from 10.2.0.3 and i thougt not in your version!
You could create views in your version, but not in a mapping and you would have to paste the self developed sql in your view definition!

Similar Messages

OWB View Issue.

am having a mapping which contains a view. The view is run on a
remote database and the mapping uses the view data as a source.
When i execute the mapping, i get 0 rows from the view.
However when i execute the view on the remote database
i get data from it.
I have deleted the view in the remote DB to see whether the
DB link was pointing to the correct view or source or not.
Infact the mapping package gives an error which shows that
its poining to the right view.
I have created a temp table in the remote DB and i source the
view to this temp table. In this case the data is captured.
I am not sure why the view is not running in the view format.
Any mapping configuration to be altered.
I am on OWB 9.2.0.4

Have you tried to use "generate intermediate results" on your source view in your mapping and copied the SQL statement in a tool like TOAD to verify the correct SQL is executed?
Regards,
Jörg

Maintenance View Validations

I have a custom table for which I am maintaining a Maintenance View.
I want to provide some validations and checks on the fields entered by the user in that maintenance view.
For example, if the user enters a value greater than 1000 in quantity field, I want to display a message saying that " enter only values below 1000". This is part of customer requirement.
Can I provide validations on fields in Maintenance view and if yes, then how ?
Thanks,
Urmila

Hi this may help u.
Maintenance views offer easy ways to maintain complex application objects.
Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.
A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for maintenance views are always derived from the foreign key (see Foreign Key Relationship and Join Condition). You cannot directly enter the join conditions as for database views.
There are some restrictions for the attributes of the foreign keys with which the tables in a maintenance view can be linked (see Restrictions for Maintenance and Help Views).
A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data from the base tables of a maintenance view together.
Maintenance mechanisms, like screens and processing programs, must be created from the view definition with the transaction Generate Table View (SE54). This makes it possible to create easy-to-use maintenance interfaces in a simple manner.
You can find out how to create such maintenance mechanisms in the documentation BC - Generate Table Maintenance Dialog.
Creating Maintenance Views
Procedure
Enter an explanatory short text in the field Short text.
You can for example find the view at a later time using this short text.
Enter the primary table of the view under Tables in the Tables/Join conditions tab page.
Only those tables that are linked with the primary table (indirectly) with a foreign key can be included in the maintenance view.
If required, include more tables in the view. In a maintenance view you can only insert tables that are linked to one another with foreign keys.
Place the cursor on the primary table and choose Relationships. All existing foreign key relationships of the primary table are displayed. Select the required foreign key and choose Copy. The secondary table used in such a foreign key is included in the view. The join conditions derived from the foreign keys (see Foreign Key Relationship and Join Condition) are displayed.
You can also insert tables that are linked by foreign key with one of the secondary tables that was already inserted. To do this, place the cursor on the secondary table and choose Relationships. Then proceed as described above.
For maintenance and help views, there are certain restrictions on the foreign keys with which the tables can be included in the view (see Restrictions for Maintenance and Help Views). The foreign keys violating these conditions are displayed at the end of the list under the header Relationships with unsuitable cardinality.
On the View fields tab page, select the fields that you want to copy to the view.
Choose Table fields. All the tables contained in the view are displayed in a dialog box. Select a table. The fields of the table are now displayed in a dialog box. You can copy fields by selecting them in the first column and choosing Copy.
All key fields of the primary table must be included in a maintenance view. In addition, all key fields of secondary tables that are not involved in the foreign key (that is, which are not linked via a join condition to a key field already included in the view) must be included in the view.
This ensures that the records inserted with a maintenance view can be written correctly in the tables contained in the view.
On the Selection conditions tab page, you can (optionally) formulate restrictions for the data records that can be displayed with the view (see Maintaining Selection Conditions for Views).
The selection conditions define the data records that can be selected with the view.
In the Maintenance status tab page, define the maintenance status of the view.
The maintenance status defines how you can access the view data with the standard maintenance transaction (SM30).
Choose .
At activation, a log is written; it can be displayed with Utilities ® Activation log. If errors or warnings occurring when the view was activated, the activation log is automatically displayed.
Go to Transaction SE54 with Environment ® Tab.maint.generator.
From the view definition you can generate maintenance modules and maintenance interfaces that distribute the data entered with the view to the base tables of the view. You can find more information in Creating a Maintenance Dialog.
Other Options
Recording documentation: You can create information about using the view with Goto ® Documentation. This documentation is output for example when you print the view.
Changing the data element of a view field: Select column Mod (modification) for the view field. The Data element field is now ready for input. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
Enter the delivery class of the view: In the Maintenance status tab page, select the delivery class of the maintenance view. If you assign the delivery class G or E to the view, you must also maintain a customer namespace (key block) for the view entries. To navigate to the appropriate maintenance transaction, choose Define Customer Namespace.
Entering the maintenance attributes of the view field: In the View fields tab page you can define the Maintenance Attributes of the view field in column F.
Check functions: With Extras ® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance screen is identical to the definitions in the runtime object of the view. With Extras ® Runtime object ® Display you can display the runtime object of the view.
table maintai9nenece generator
The Table Maintenance Generator is used to create table maintenance program to add, modify or delete records in the database table. This can be accessed using transaction SE54 or in SE11 using the menu Utilities->Table Maintenance Generator.
Table maintenance allows you to create entries for that table
Follow these steps to generate table maintenance
1) Go to SE11 and check table maintanance check box under attributes tab.
2) Go to menu Utilities -> Table Maintanance Generator ->
Create function group and assign it under function group input box. You can enter same as table name for function group. Also assign authorization group default &NC& .
3) Select standard recording routine radio in table table mainitainence generator to move table contents to quality and production by assigning it to request.
4) Select maintenance type as single step.
5) Maintainence screen as system generated numbers this dialog box appears when you click on create button.
6) Save and activate table.
useful links
http://www.saptechies.com/how-to-create-table-maintenance-generator/
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ecdf446011d189700000e8322d00/content.htm
http://www.saptechies.com/table-maintainance-generator/
with regards,
Hema Sundara.
pls reward if u find it helpful.

Package in owb views

In OWB 10.2 views, all_iv_functions,for a particular function, we get the package names as a function library name.
These packages are created in a project,but the schema id for the packages in the the above view is blank.
How can we get the information as to which module the package belongs to.
Thanks ...

you should be able to find this in owb_repowner schema

Lookup View Validation Refresh

Hello,
I have a view defined with Trinidad components only. There I use the follwoing:
<tr:selectOneChoice label="Label 1" binding="#{homePageBean.selectOneChoiceRubrikIs1}"
id="s1" immediate="true"
autoSubmit="true"
valueChangeListener="#{homePageBean.selectOneChoiceRubrikIs1VL}">
<tr:selectItem label="Choose" />
<tr:selectItem label="Big 5" value="1"
binding="#{homePageBean.selectItemCategoryIs1}"/>
</tr:selectOneChoice>
Within the managed bean in the method 'selectOneChoiceRubrikIs1VL' I lookup a view using some binding variables.
In the log I see the following during the first element will be read.
<DCBindingContainer> <validateInputValues> [1239] DCBindingContainer:oracle_fodemo_storefront_indexPageDef no validations performed
<ADFLogger> <begin> Refreshing binding container
<DCBindingContainer> <internalRefreshControl> [1240] **** refreshControl() for BindingContainer :oracle_fodemo_storefront_indexPageDef
<ADFLogger> <end> Refreshing binding container
The content for the first element is null. Then the next element will be read. I never get the first one.
I use JDeveloper 11.1.2.0.0.
How can I avoid this behaviour.
Any help will be greatly appreciated. Thanks in advance.
Best regards
Martin

Hi,
What is the purpose of bindings of <tr:selectItem label="Big 5" value="2" binding="#{homePageBean.selectItemCategoryIs1}"/> can you try this
<tr:selectOneChoice label="Label 1" binding="#{homePageBean.selectOneChoiceRubrikIs1}"
id="s1" immediate="true"
autoSubmit="true"
valueChangeListener="#{homePageBean.selectOneChoiceRubrikIs1VL}">
<tr:selectItem label="Choose" value="1"/>
<tr:selectItem label="Big 5" value="2" >
</tr:selectOneChoice>Please share source code in Bean

BestPratice: OWB Load Validation Tables?

Hello All:
Quick Question:
I have multiple dozens of Validation (lookup, PK-FK, Metadata, Dim) tables that In the past I created and loaded with a sql script:
create table vjnk ....;
insert into vjunk( ....;
insert into vjunk( ....;
What would be the best way to manage these tables in OWB?
A few Ideas are:
Use XL or some flat file format and external table then have an insert/update mapping?
Do a table export on current tables but then what? (naaaa)
Use an Insert Script? (Don't think so)
I am sure the OWB gurus have a plan for this kind of table load?
Thanks
A

I was wondering what you meant by 'XL' ...
Still what you mean by how to manage these lookup tables in OWB? Do you need to continue to manually add to/update the contents of them? The recommended way of loading flat files is through external tables. If the source is Excel you can load it directly through ODBC with Oracle Heterogeneous Services.
Nikolai Rochnik

Some problems and questions using OWB

For Igor or anyone who can help me :-)
Hello Igor,
Thanks for all your help concerning my mapping deployment problem! Now its working better ;-)
I used the OWB Runtime Assistant to create a new runtime target schema and i use the owner of this schema as user while logging to OWB.
Now i can create and deploy without problems mappings, tables, functions, procedures, packages, dimensions, views, materialized views, process flows (i have installed the Oracle Workflow Client 2.6.2.0.0 with OWF builder and OWF mailer ).
However I have still some problems and questions :-)
a) After deploying a mapping or process flow i can execute them from OWB Deployment Manager. How can i schedule the execution of a deployed precess without using OWBDM ? (I want to execute a process every day to perform ETL).
b) I think i have a problem deploying cubes. I create a cube in OWB, the validation is OK, the deploment succeds, but if i look with OEMC in the tree in the Warehouse OLAP section no cube is created. Only the fact tabe is created. If i look to the scripts from the Pre Deployment generation results i found DDLs only for TABLE, INDEX, UNIQUE KEY, FOREIGN KEY and ANALYZE object types, meanwhile during a dimension deployment i found also a DDL for the DIMENSION type object. WHY ?
c) If I look in the procedures of the new created OWB Runtime Target Schema I found 3 procedures which are in error and when I try to compile them I receive the following error messages :
- procedure WB_OLAP_LOAD_CUBE
PLS-00201: identifier 'DBMS_AWM.CREATE_AWCUBELOAD_SPEC' must be declared
- procedure WB_OLAP_LOAD_DIMENSION
PLS-00201: identifier 'DBMS_AWM.CREATE_AWDIMLOAD_SPEC' must be declared
- procedure WB_OLAP_LOAD_DIMENSION_GENUK
PLS-00201: identifier 'DBMS_AWM.CREATE_AWDIMLOAD_SPEC' must be declared
How can solve this problem? Is there any link with the fact that the cube is not generated?
d) When I first acces the deployed DIM in the OEMC tree I receive a message saying that the dimension does not have complete metadata as needed for use by Oracle OLAP services (because is created either in an earlier version of Oracle database or it was created by an an other application than OEMC) and OEMC automatically generates the default needed metadata. Is this normal ?
I work in an environment with
- Oracle 9i Database 9.2.0.1.0
- Oracle 9i Client 9.2.0.1.0
- Oracle 9i Warehouse Builder Products 9.2.0.2.8
Best Regards:
Vlad
PS Sorry for my poor English ;-)

Answered in your "Getting RPE-01008 when deploying mappings" post.
Regards:
Igor

Build in OWB and make map in AWM?

Hi all,
Would it be possible to design and deploy the dimensional objects (dims/cubes) using OWB and make a mapping to populate them using AWM? These are all MOLAP objects. The advantage of designing in OWB is the editor and e.g. the ability to add calculated measures in cubes using the wizard.
Just did a quick test. When deploying a MOLAP dimension from OWB, in AWM it shows the map with several OWB-generated views to populate the object. I don't want to use those since I don't want to build a map in OWB. I have a simple 1-to-1 view to populate the object in AWM. However, when removing the OWB views from the map in AWM and replacing it by my view, when applying the changes it comes back with an error:
An error occurred creating DimensionMapGroup D_DIM_EMPLOYEE_M.TOTAL.MAPGROUP1.DIMENSIONMAPGROUP : ***Error Occured in DELETE_MAPPING_GROUP: You provided extra input starting at '$'.
The error detail window shows:
oracle.AWXML.AWException: An error occurred creating DimensionMapGroup D_DIM_EMPLOYEE_M.TOTAL.MAPGROUP1.DIMENSIONMAPGROUP : ***Error Occured in DELETE_MAPPING_GROUP: You provided extra input starting at '$'.
at oracle.AWXML.MappingGroup.Delete(MappingGroup.java:125)
at oracle.olap.awm.dataobject.modeler.ModelDO.deleteObjectInAW(ModelDO.java:533)
at oracle.olap.awm.dataobject.modeler.ModelDO.deleteAllMaps(ModelDO.java:1937)
at oracle.olap.awm.dataobject.modeler.DimensionDO.createMaps(DimensionDO.java:589)
at oracle.olap.awm.dataobject.modeler.DimensionDO.update(DimensionDO.java:746)
at oracle.olap.awm.dataobject.dialog.PropertyViewer.doApplyAction(PropertyViewer.java:770)
at oracle.olap.awm.dataobject.dialog.PropertyViewer.access$200(PropertyViewer.java:54)
at oracle.olap.awm.dataobject.dialog.PropertyViewer$1ApplyThread.run(PropertyViewer.java:550)
If this doesn't work it's just another blow to our olap-in-oracle implementation plan.
Does anybody have experience with this issue?
Thanks,
Ed

You'd better make the reservation of Genius Bar and show them about your problem.

ORA-19201: Datatype not supported when validating XML against an XSD

Hello.
Info: using Oracle 10.2.0.1.0, Java components are installed.
I've created an XML view using ora:view, which is validated against a registered XSD. This view is created successfully.
But when I SELECT * from this view, it gives ORA-19201 - Datatype not supported.
Can't understand why. I've matched the XML to the XSD, and the datatypes all look fine to me. I've referred to the XSD using the XMLFORMAT.CREATEFORMAT option. When I use the same option to specify "NO_SCHEMA", it returns the correct XML, but we need to validate it against the XSD.
I'm thinking one of two things has happened here:
1. I've made a mistake with either my registration, or how I've used XMLFORMAT to refer to the XSD.
2. There's a bug in Oracle.
My money's on 1. Can anyone help?
Thanks,
Ray.

Hello Geoff, I didn't want to send any code until I knew someone was willing to look at it (there's a lot of it).
Here is the XSD:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
     <xs:element name="TransInfo">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="PIE_ERROR" type="PIE_ERRORType" minOccurs="0"/>
                    <xs:element name="Transaction" type="TransactionType" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="PIE_ERRORType">
          <xs:sequence>
               <xs:element ref="ERROR_CODE"/>
               <xs:element ref="DESCRIPTION"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="ERROR_CODE">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="0001"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="DESCRIPTION">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="LEAD NUMBER 12345 IS INVALID"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="TransactionType">
          <xs:sequence>
               <xs:element ref="TRANSACTION_NUMBER"/>
               <xs:element ref="TRANSACTION_STATUS"/>
<xs:element ref="CONTACT_ID"/>
               <xs:element ref="INVOICE_NUMBER"/>
               <xs:element ref="CHANNEL"/>
               <xs:element ref="CSA"/>
               <xs:element ref="OPEN_DATETIME"/>
               <xs:element ref="CLOSED_DATETIME"/>
               <xs:element name="Orderline" type="OrderlineType" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="TRANSACTION_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="3455229"/>
                    <xs:enumeration value="3455230"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TRANSACTION_STATUS">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="C"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CONTACT_ID">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="111"/>
                    <xs:enumeration value="222"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="INVOICE_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="123456789"/>
                    <xs:enumeration value="987654321"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CHANNEL">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Test 1"/>
                    <xs:enumeration value="Test 2"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CSA">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="SEARLEA"/>
                    <xs:enumeration value="SILVAJ"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="OPEN_DATETIME">
          <xs:simpleType>
               <xs:restriction base="xs:dateTime">
                    <xs:enumeration value="2001-10-26T20:32:52"/>
                    <xs:enumeration value="2004-12-06T10:23:25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CLOSED_DATETIME">
          <xs:simpleType>
               <xs:restriction base="xs:dateTime">
                    <xs:enumeration value="2001-10-26T21:32:52"/>
                    <xs:enumeration value="2004-12-06T10:23:25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="OrderlineType">
          <xs:sequence>
               <xs:element ref="ORDER_QTY"/>
               <xs:element ref="RETAIL_AMT"/>
               <xs:element ref="SALE_AMT"/>
               <xs:element ref="PRODUCT_DESCR"/>
               <xs:element ref="PART"/>
               <xs:element ref="IMEI"/>
               <xs:element name="BankDetails" type="BankDetailsType"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="ORDER_QTY">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="1"/>
                    <xs:enumeration value="3"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="RETAIL_AMT">
          <xs:simpleType>
               <xs:restriction base="xs:decimal">
                    <xs:enumeration value="45.67"/>
                    <xs:enumeration value="54.76"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="SALE_AMT">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="45.67"/>
                    <xs:enumeration value="54.76"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PRODUCT_DESCR">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Product test 2"/>
                    <xs:enumeration value="Vodafone Nokia 6230 Pack"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PART">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="6806"/>
                    <xs:enumeration value="8606"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="IMEI">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="099000000000001"/>
                    <xs:enumeration value="09900078900001"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="BankDetailsType">
          <xs:sequence>
               <xs:element ref="BANK_NAME"/>
               <xs:element ref="ACCOUNT_NAME"/>
               <xs:element ref="ACCOUNT_NUMBER"/>
               <xs:element ref="SORT_CODE"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="BANK_NAME">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="HSBC"/>
                    <xs:enumeration value="LLOYDS"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="ACCOUNT_NAME">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="MR A SEARLE"/>
                    <xs:enumeration value="MR J SILVA"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="ACCOUNT_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="87698789"/>
                    <xs:enumeration value="89769082"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="SORT_CODE">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="100928"/>
                    <xs:enumeration value="123346"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
</xs:schema>
I then registered this XSD using DBMS_XMLSCHEMA.REGISTER, calling it test_1.xsd. It is visble in USER_XML_SCHEMAS.
Here are the 15 views used to drive the XML:
SQL> desc v_pie_branch
Name Null? Type
BRANCH NOT NULL NUMBER(4)
SQL> desc v_pie_branch_feature
Name Null? Type
BRANCH_FEATURE NOT NULL NUMBER(10)
BRANCH NUMBER(4)
FEATURE_TYPE VARCHAR2(10)
CHANNEL VARCHAR2(40)
SQL> desc v_pie_transaction
Name Null? Type
TRANSACTION_NUMBER NOT NULL NUMBER(10)
BRANCH NUMBER(4)
EMPLOYEE_TRANS VARCHAR2(12)
CONTACT NUMBER(8)
OPEN_DAT DATE
OPEN_TIM DATE
TRANSACTION_STATUS VARCHAR2(1)
TRANS_TYPE VARCHAR2(1)
CLOSED_DAT DATE
CLOSED_TIM DATE
INVOICE_NUMBER NUMBER(10)
INVOICE_DAT DATE
CSA VARCHAR2(12)
CREATED_ON DATE
AMENDED_BY VARCHAR2(12)
AMENDED_ON DATE
OPEN_DATETIME VARCHAR2(19)
CLOSED_DATETIME VARCHAR2(19)
SQL> desc v_pie_bank_detail
Name Null? Type
BANK_DETAIL NOT NULL NUMBER(12)
BANKCODE VARCHAR2(40)
SORTCODE VARCHAR2(40)
BANK_NAME VARCHAR2(60)
SQL> desc v_pie_account_detail
Name Null? Type
ACCOUNT_DETAIL NOT NULL NUMBER(12)
BANK_DETAIL NUMBER(12)
ACCOUNT_NUMBER VARCHAR2(40)
SORT_CODE VARCHAR2(40)
ACCOUNT_NAME VARCHAR2(40)
BANKCODE VARCHAR2(40)
SQL> desc v_pie_account_link
Name Null? Type
ACCOUNT_LINK NOT NULL NUMBER(12)
CONTACT NUMBER(12)
ACCOUNT_DETAIL NUMBER(12)
ACC_LINK_TYP NUMBER(12)
BNK_SINCE DATE
AC_DET VARCHAR2(40)
SQL> desc v_pie_compesn
Name Null? Type
COMPESN NOT NULL NUMBER(10)
CONTACT NUMBER(8)
IMEI VARCHAR2(25)
SQL> desc v_pie_contact
Name Null? Type
CONTACT_ID NOT NULL NUMBER(8)
CONTACT_TYP VARCHAR2(1)
COMPANY NUMBER(10)
BRANCH NUMBER(4)
DEAD_FLG VARCHAR2(1)
FORENAME VARCHAR2(20)
TITLE VARCHAR2(5)
MID_INITIAL VARCHAR2(1)
GENDER VARCHAR2(1)
FRAUD_FLG VARCHAR2(1)
SQL> desc v_pie_servcon
Name Null? Type
SERVCON NOT NULL NUMBER(10)
CONTRACT NUMBER(10)
CONNECTION_CURR NUMBER(10)
CONTACT NUMBER(8)
SQL> desc v_pie_tpplan_compline
Name Null? Type
TPPLAN_COMPLINE NOT NULL NUMBER(10)
SERVCON NUMBER(10)
PPLAN NUMBER(10)
SQL> desc v_pie_tpplan_comp_detail
Name Null? Type
TPPLAN_COMPLINE NOT NULL NUMBER(10)
RULE_DETAIL_NO NOT NULL VARCHAR2(5)
RULE_DETAIL_LINE NOT NULL NUMBER(2)
U_VERSION VARCHAR2(1)
OPTION VARCHAR2(40)
OPT_STRING VARCHAR2(40)
SQL> desc v_pie_tpplan
Name Null? Type
SERVCON NOT NULL NUMBER(10)
PPLAN NOT NULL NUMBER(10)
U_VERSION VARCHAR2(1)
SQL> desc v_pie_connection
Name Null? Type
CONNECTION NOT NULL NUMBER(10)
CONTACT NUMBER(8)
ADDRESSNO NUMBER(5)
TRANSACTION NUMBER(10)
TPRODLINE NUMBER(10)
CONTRACT NUMBER(10)
SERVCON NUMBER(10)
SQL> desc v_pie_tprodline
Name Null? Type
TRANSACTION NOT NULL NUMBER(10)
TPRODLINE NOT NULL NUMBER(10)
CONTACT NUMBER(8)
PRODUCT NUMBER(10)
ORDER_QTY NUMBER(12)
RETAIL_AMT NUMBER
SALE_AMT NUMBER
SQL> desc v_pie_product
Name Null? Type
PRODUCT NOT NULL NUMBER(10)
PART VARCHAR2(20)
PRODUCT_DESCR VARCHAR2(40)
This is the code to create an XML view, validating against the schema:
create OR REPLACE VIEW v_xml_validate AS
SELECT SYS_XMLAGG(XMLQuery('
<PIE_ERROR>
<ERROR_CODE>"0001"</ERROR_CODE>
<DESCRIPTION>"There was an error with this customer"</DESCRIPTION>
</PIE_ERROR>,
<Transaction>
{for $t in ora:view("V_PIE_TRANSACTION")/ROW
    ,$ct in ora:view("V_PIE_CONTACT")/ROW
    ,$b in ora:view("V_PIE_BRANCH")/ROW
    ,$bf in ora:view("V_PIE_BRANCH_FEATURE")/ROW
where $t/CONTACT = $ct/CONTACT_ID
and   $t/BRANCH = $b/BRANCH
and   $b/BRANCH = $bf/BRANCH
return ($t/TRANSACTION_NUMBER
        ,$t/TRANSACTION_STATUS
        ,$ct/CONTACT_ID
        ,$t/INVOICE_NUMBER
        ,$bf/CHANNEL
        ,$t/CSA
        ,$t/OPEN_DATETIME
        ,$t/CLOSED_DATETIME
        ,<Orderline>
              {for $tpl in ora:view("V_PIE_TPRODLINE")/ROW
                  ,$pr in ora:view("V_PIE_PRODUCT")/ROW
                  ,$cmpesn in ora:view("V_PIE_COMPESN")/ROW
               where $tpl/TRANSACTION eq $t/TRANSACTION_NUMBER
               and   $tpl/PRODUCT eq $pr/PRODUCT
               and   $ct/CONTACT_ID eq $cmpesn/CONTACT
               return ($tpl/ORDER_QTY
                      ,$tpl/RETAIL_AMT
                      ,$tpl/SALE_AMT
                      ,$pr/PRODUCT_DESCR
                      ,$pr/PART
                      ,$cmpesn/IMEI
                      ,<BankDetails>
                           {for $conn in ora:view("V_PIE_CONNECTION")/ROW
                            for $scon in ora:view("V_PIE_SERVCON")/ROW
                            for $tpp in ora:view("V_PIE_TPPLAN")/ROW
                            for $tppc in ora:view("V_PIE_TPPLAN_COMPLINE")/ROW
                            for $tppcd in ora:view("V_PIE_TPPLAN_COMP_DETAIL")/ROW
                            for $al in ora:view("V_PIE_ACCOUNT_LINK")/ROW
                            for $ad in ora:view("V_PIE_ACCOUNT_DETAIL")/ROW
                            for $bd in ora:view("V_PIE_BANK_DETAIL")/ROW
                            where $conn/CONTACT eq $ct/CONTACT_ID
                            and   $scon/CONTACT eq $conn/CONTACT
                            and   $tpp/SERVCON eq $scon/SERVCON
                            and   $tppc/SERVCON eq $tpp/SERVCON
                            and   $tppc/PPLAN eq $tpp/PPLAN
                            and   $tppcd/TPPLAN_COMPLINE eq $tppc/TPPLAN_COMPLINE
                            and   $al/AC_DET eq $tppcd/OPT_STRING
                            and   $ad/ACCOUNT_DETAIL eq $al/ACCOUNT_DETAIL
                            and   $bd/BANK_DETAIL eq $ad/BANK_DETAIL
                            return ($bd/BANK_NAME
                                   ,$ad/ACCOUNT_NAME
                                   ,$ad/ACCOUNT_NUMBER
                                   ,$ad/SORT_CODE
</BankDetails>
</Orderline>
</Transaction>'
RETURNING CONTENT),
XMLFORMAT.CREATEFORMAT('TransInfo','USE_GIVEN_SCHEMA','test_1.xsd', 'http://xmlns.cpw.co.uk/CPW/EPOS/Order/RetrieveTransaction/RetrieveTransaction', NULL, NULL)) AS xml_string FROM DUAL;
The view is created with no errors. Selecting * from it, however, gives:
ORA-19201 - Datatype not supported
Marrying the XML to the XSD shows nothing obviously wrong.
Thanks,
Ray.

Sound notification on touch validity fingerprint

can i disable sound notifications of windows 8 when i touch validity fingerprint??? because while i write on my notebook (hp probook 430 g1) i touch validity fingerprints with palm of my hand and i receive this warning on events viewer: Validity USDK
this because my palm is not my fingerprint
these notifications are so annoying!!!!

HI tafazzi87:
Thank you for your inquiry.
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product.. You can do this at http://h30499.www3.hp.com/hpeb/ .
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Public Sector Budget Validation Error

Hello all,
While Freeze the Budget I got error for Validate Budget Group Hierarchy concurrent Program. Below I am submitting the log output.
The program failed with the following errors :
Account 03.620.0.246.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.11.0.2211008.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2211313.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.122.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.130205.246.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2211204.0 has budgeting enabled but does not belong to any budget group.
Account 03.0.0.0.0.6510134.0 has budgeting enabled but does not belong to any budget group.
Account 03.0.0.0.0.2990109.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.10302.3102.310001.1450105.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.11.0.2211313.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.130205.0.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.0.0.0.0.6510135.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.135.0.2211008.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.135.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2220211.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2110322.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.11.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.5420.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.246.0.2211008.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.130205.246.431001.1450105.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2211008.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.0.246.0.1140703.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.2110329.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.130205.0.0.1140703.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.130205.0.0.2110319.0 has budgeting enabled but does not belong to any budget group.
Account 03.615.0.4414.0.2220211.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.1420401.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.4309.0.1140502.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.10302.3102.310001.1450405.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.243.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.0.0.0.0.6510136.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.3102.0.2210101.0 has budgeting enabled but does not belong to any budget group.
Account 03.620.0.11.0.2220211.0 has budgeting enabled but does not belong to any budget group.
Account 03.0.0.0.0.9900001.0 has budgeting enabled but does not belong to any budget group.
The program failed with the following errors :
The budget group has not been frozen due to validation errors. Please check the errors by checking the Error Messages Report or the View Validations screen of the Budget Group form for the root budget group.
There are warnings detected due to account range test of "Includes" only ranges, or accounts not in any budget group of the hierarchy that are budgetary accounts in GL, or missing or invalid Organization.
These warning messages are treated as errors when you choose not to force freeze or when you choose to force freeze but errors are detected.
Please choose to force freeze the budget group if warning messages will not affect the worksheet and there are no error messages like duplicate account combination.
Please explain me what would be the issue.
Thanks and Regards,
Muthu
[email protected]

you can find the public sector budget guide from the following link
http://download.oracle.com/docs/cd/B34956_01/current/acrobat/120psbug.zip
Message was edited by:
Ramsys

Views Automatically invalidated

Hi
I have created some force views in my database. Every morning when i check the invalid objects these views are automactically invalidated. When i compile them they get valid and again the next day they become invalid.
The view is a join of 2-3 tables and every night one of the tables is truncated, the indexes are dropped ,data inserted and indexes are recreated.
Any other ddl is not fired on any of the tables in the view.
The version of oracle :
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Regards
Ankit

Problem lies with your index recreation. The indexed columns are referenced in your view. Below example will illustrate my point.
SQL>
SQL> select * from rag;
       NID        SID
         1        100
         2        200
         3        200
         5        200
         6        100
         8        200
         9        100
7 rows selected.
SQL> create unique index RAG_UK ON RAG(NID);
Index created.
SQL> create view RAG_VIEW AS select NID,NID+10 Val from RAG;
View created.
SQL> select object_name,object_type,status from
2 user_objects where object_name='RAG_VIEW';
OBJECT_NAME                                                                                                                      OBJECT_TYPE         STATUS
RAG_VIEW                                                                                                                         VIEW                VALID
SQL> drop index RAG_UK;
Index dropped.
SQL> create unique index RAG_UK ON RAG(NID);
Index created.
SQL> select object_name,object_type,status from
2   user_objects where object_name='RAG_VIEW';
OBJECT_NAME                                                                                                                      OBJECT_TYPE         STATUS
RAG_VIEW                                                                                                                         VIEW                INVALID

Compile view

hii
i have a question
if i create a view v1 on t1 table with column first_name,employee_id,last_name
as
create view v1 as select from t1;*
now i drop a column from the table say employee_id
n when now i issue select * from v1 i will get error
but if i am issuing command
alter view v1 compile
but still i am not able to use
select from v1*
can you suggest me can i solve it without recreating view

Let us start with the earlier example.
We have created a view and it is valid in status.
$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 11 17:34:02 2011
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> desc test_emp
Name                                      Null?    Type
EMPNO                                              NUMBER(4)
ENAME                                              VARCHAR2(10)
JOB                                                VARCHAR2(9)
MGR                                                NUMBER(4)
HIREDATE                                           DATE
SAL                                                NUMBER(7,2)
COMM                                               NUMBER(7,2)
DEPTNO                                             NUMBER(2)
SQL> CREATE OR REPLACE VIEW tst_emp_view AS SELECT * FROM test_emp;
View created.
SQL> set long 10000
SQL> SELECT view_name,text FROM user_views WHERE view_name='TEST_EMP_VIEW';
no rows selected
SQL> ed
Wrote file afiedt.buf
1* SELECT view_name,text FROM user_views WHERE view_name='TST_EMP_VIEW'
SQL> /
VIEW_NAME
TEXT
TST_EMP_VIEW
SELECT "EMPNO","ENAME","JOB","MGR","HIREDATE","SAL","COMM","DEPTNO" FROM test_em
p
SQL> SELECT object_name,object_type,status FROM
2 user_objects WHERE object_name='TST_EMP_VIEW';
OBJECT_NAME
OBJECT_TYPE         STATUS
TST_EMP_VIEW
VIEW                VALIDNow, We have added a column to the table and the view becomes invalid.
SQL> ALTER TABLE test_emp ADD test_col VARCHAR2(1);
Table altered.
SQL> ed
Wrote file afiedt.buf
1 SELECT object_name,object_type,status FROM
2*     user_objects WHERE object_name='TST_EMP_VIEW'
SQL> /
OBJECT_NAME
OBJECT_TYPE         STATUS
TST_EMP_VIEW
VIEW                INVALID
SQL> ALTER VIEW tst_emp_view COMPILE;
View altered.
SQL> SELECT object_name,object_type,status FROM
2 user_objects WHERE object_name='TST_EMP_VIEW';
OBJECT_NAME
OBJECT_TYPE         STATUS
TST_EMP_VIEW
VIEW                VALID
SQL> SELECT view_name,text FROM user_views WHERE view_name='TST_EMP_VIEW'
2 ;
VIEW_NAME
TEXT
TST_EMP_VIEW
SELECT "EMPNO","ENAME","JOB","MGR","HIREDATE","SAL","COMM","DEPTNO" FROM test_em
pSo, the view becomes VALID through "ALTER" command. Because the damage is repairable.
But, As explained earlier, If we drop a column then:
SQL> ALTER TABLE test_emp drop column sal;
Table altered.
SQL> SELECT object_name,object_type,status FROM
2   user_objects WHERE object_name='TST_EMP_VIEW';
OBJECT_NAME
OBJECT_TYPE         STATUS
TST_EMP_VIEW
VIEW                INVALID
SQL> ALTER VIEW tst_emp_view COMPILE;
Warning: View altered with compilation errors.
SQL>Another scenario could be modifying a column (may be data type length)
SQL> CREATE OR REPLACE VIEW tst_emp_view AS SELECT * FROM test_emp;
View created.
SQL> SELECT object_name,object_type,status FROM
2 user_objects WHERE object_name='TST_EMP_VIEW';
OBJECT_NAME
OBJECT_TYPE         STATUS
TST_EMP_VIEW
VIEW                VALID
SQL> ALTER TABLE test_emp MODIFY ename VARCHAR2(100);
Table altered.
SQL> SELECT object_name,object_type,status FROM
2 user_objects WHERE object_name='TST_EMP_VIEW';
OBJECT_NAME
OBJECT_TYPE         STATUS
TST_EMP_VIEW
VIEW                INVALID
SQL> ALTER VIEW tst_emp_view COMPILE;
View altered.
SQL>

How to add image in virtual dir / i/ 11g when using the embedded gateway

Hi,
Does somebody knows how to 'simple' import a file or directory
into the /images/ or /i/ directory created by APEX without tricks like in How I added a new image to APEX in 11g when using the embedded gateway.
when using Database 11g with the embedded gateway. with webdav of ftp.
When I use the url http://localhost/images
I need to logon.
There is not 1 username/password that I can use. I tried all.
When I try http://localhost/i/16admin.gif then the gif is shown.
I must be something with ACL's or DBMS_EPG or maybe the default port 80 that I use?
My configuration is
Doing 11.1.0.6.0 checks
############# Status/Version #############
XDB Status is: VALID at version 11.1.0.6.0
############# OTHER DATABASE FEATURES #############
Oracle Application Express is VALID at version 3.1.2.00.02
OWB is VALID at version 11.1.0.6.0
Oracle Enterprise Manager is VALID at version 11.1.0.6.0
Oracle Ultra Search is VALID at version 11.1.0.6.0
OLAP Catalog is VALID at version 11.1.0.6.0
Spatial is VALID at version 11.1.0.6.0
Oracle Multimedia is VALID at version 11.1.0.6.0
Oracle XML Database is VALID at version 11.1.0.6.0
Oracle Text is VALID at version 11.1.0.6.0
Oracle Expression Filter is VALID at version 11.1.0.6.0
Oracle Rules Manager is VALID at version 11.1.0.6.0
Oracle Workspace Manager is VALID at version 11.1.0.6.0
Oracle Database Catalog Views is VALID at version 11.1.0.6.0
Oracle Database Packages and Types is VALID at version 11.1.0.6.0
JServer JAVA Virtual Machine is VALID at version 11.1.0.6.0
Oracle XDK is VALID at version 11.1.0.6.0
Oracle Database Java Packages is VALID at version 11.1.0.6.0
OLAP Analytic Workspace is VALID at version 11.1.0.6.0
Oracle OLAP API is VALID at version 11.1.0.6.0
############# XDBCONFIG INFORMATION #############
acl-max-age= = = 15
acl-cache-size= = = 32
case-sensitive= = = true
call-timeout= = = 6000
max-link-queue= = = 65536
max-session-use= = = 100
persistent-sessions= = = false
default-lock-timeout= = = 3600
xdbcore-logfile-path= = = /sys/log/xdblog.xml
xdbcore-log-level= = = 0
resource-view-cache-size= = = 1048576
extension= = = au
mime-type= = = audio/basic
extension= = = avi
mime-type= = = video/x-msvideo
extension= = = bin
mime-type= = = application/octet-stream
extension= = = bmp
mime-type= = = image/bmp
extension= = = css
mime-type= = = text/css
extension= = = doc
mime-type= = = application/msword
extension= = = eml
mime-type= = = message/rfc822
extension= = = gif
mime-type= = = image/gif
extension= = = htm
mime-type= = = text/html
extension= = = html
mime-type= = = text/html
extension= = = jpe
mime-type= = = image/jpeg
extension= = = jpeg
mime-type= = = image/jpeg
extension= = = jpg
mime-type= = = image/jpeg
extension= = = js
mime-type= = = application/x-javascript
extension= = = jsp
mime-type= = = text/html
extension= = = mid
mime-type= = = audio/mid
extension= = = mov
mime-type= = = video/quicktime
extension= = = movie
mime-type= = = video/x-sgi-movie
extension= = = mp3
mime-type= = = audio/mpeg
extension= = = mpe
mime-type= = = video/mpg
extension= = = mpeg
mime-type= = = video/mpg
extension= = = mpg
mime-type= = = video/mpg
extension= = = msa
mime-type= = = application/x-msaccess
extension= = = msw
mime-type= = = application/x-msworks-wp
extension= = = pcx
mime-type= = = application/x-pc-paintbrush
extension= = = pdf
mime-type= = = application/pdf
extension= = = png
mime-type= = = image/png
extension= = = ppt
mime-type= = = application/vnd.ms-powerpoint
extension= = = ps
mime-type= = = application/postscript
extension= = = qt
mime-type= = = video/quicktime
extension= = = ra
mime-type= = = audio/x-realaudio
extension= = = ram
mime-type= = = audio/x-realaudio
extension= = = rm
mime-type= = = audio/x-realaudio
extension= = = rtf
mime-type= = = application/rtf
extension= = = rv
mime-type= = = video/x-realvideo
extension= = = sgml
mime-type= = = text/sgml
extension= = = svg
mime-type= = = image/svg+xml
extension= = = tif
mime-type= = = image/tiff
extension= = = tiff
mime-type= = = image/tiff
extension= = = txt
mime-type= = = text/plain
extension= = = url
mime-type= = = text/plain
extension= = = vrml
mime-type= = = x-world/x-vrml
extension= = = wav
mime-type= = = audio/wav
extension= = = wpd
mime-type= = = application/wordperfect5.1
extension= = = xls
mime-type= = = application/vnd.ms-excel
extension= = = xml
mime-type= = = text/xml
extension= = = xsd
mime-type= = = text/xml
extension= = = xsl
mime-type= = = text/xml
extension= = = zip
mime-type= = = application/x-zip-compressed
extension= = = htc
mime-type= = = text/x-component
extension= = = xbl
mime-type= = = text/xml
extension= = = en
lang= = = english
extension= = = gzip
encoding= = = zip file
extension= = = tar
encoding= = = tar file
session-pool-size= = = 50
session-timeout= = = 6000
ftp-port= = = 0
ftp-listener= = = local_listener
ftp-protocol= = = tcp
logfile-path= = = /sys/log/ftplog.xml
log-level= = = 0
session-timeout= = = 6000
buffer-size= = = 8192
http-port= = = 80
http-listener= = = local_listener
http-protocol= = = tcp
max-http-headers= = = 64
max-header-size= = = 16384
max-request-body= = = 2000000000
session-timeout= = = 6000
server-name= = = XDB HTTP Server
logfile-path= = = /sys/log/httplog.xml
log-level= = = 0
servlet-realm= = = Basic realm="XDB"
welcome-file= = = index.html
welcome-file= = = index.htm
servlet-pattern= = = /Test
servlet-name= = = TestServlet
servlet-pattern= = = /oradb/*
servlet-name= = = DBURIServlet
servlet-pattern= = = /orarep/*
servlet-name= = = ReportFmwkServlet
servlet-pattern= = = /i/*
servlet-name= = = PublishedContentServlet
servlet-pattern= = = /apex/*
servlet-name= = = APEX
servlet-pattern= = = /images/*
servlet-name= = = IMAGES
servlet-name= = = TestServlet
servlet-language= = = Java
display-name= = = XDB Test Servlet
description= = = A servlet to test the internals of the XDB Servlet API
servlet-class= = = xdbtserv
servlet-schema= = = xdb
servlet-name= = = DBURIServlet
servlet-language= = = C
display-name= = = DBURI
description= = = Servlet for accessing DBURIs
role-name= = = authenticatedUser
role-link= = = authenticatedUser
servlet-name= = = ReportFmwkServlet
servlet-language= = = C
display-name= = = REPT
description= = = Servlet for accessing reports
role-name= = = authenticatedUser
role-link= = = authenticatedUser
servlet-name= = = PublishedContentServlet
servlet-language= = = C
display-name= = = Unauthenticated File Access Servlet
description= = = Servlet for files for unauthenticated users
param-name= = = RootFolder
param-value= = = /images
description= = = RootFolder
role-name= = = anonymousServletRole
role-link= = = anonymousServletRole
servlet-name= = = APEX
servlet-language= = = PL/SQL
display-name= = = APEX
database-username= = = ANONYMOUS
default-page= = = apex
document-table-name= = = wwv_flow_file_objects$
document-path= = = docs
document-procedure= = = wwv_flow_file_mgr.process_download
nls-language= = = american_america.al32utf8
request-validation-function= = = wwv_flow_epg_include_modules.authorize
role-name= = = anonymousServletRole
role-link= = = anonymousServletRole
servlet-name= = = IMAGES
servlet-language= = = PL/SQL
display-name= = = IMAGES
database-username= = = APS
role-name= = = anonymousServletRole
role-link= = = anonymousServletRole
allow-mechanism= = = basic
nonce-timeout= = = 300
xdbcore-xobmem-bound= = = 1024
xdbcore-loadableunit-size= = = 16
acl-evaluation-method= = = ace-order
############# XMLTYPE Tables #############
XDB has 1 XMLTYPE TABLES stored as CLOB
XDB has 24 XMLTYPE TABLES stored as OBJECT-RELATIONAL
XDB has 11 XMLTYPE TABLES stored as BINARY
############# XMLTYPE Columns #############
XDB has 3 XMLTYPE Columns stored as CLOB
MDSYS has 24 XMLTYPE Columns stored as CLOB
SYS has 1 XMLTYPE Columns stored as CLOB
ORDSYS has 9 XMLTYPE Columns stored as CLOB
############# XMLTYPE Views #############
############# XMLTYPE INDEXES #############
XDB has 1 XMLTYPE Indexes of type CSX
############# Items built with XML API's #############
PACKAGE BODY FLOWS_030100.WWV_FLOW_XLIFF
PACKAGE BODY FLOWS_030000.WWV_FLOW_XLIFF
PACKAGE BODY MDSYS.SDO_WFS_PROCESS
PACKAGE BODY EXFSYS.DBMS_RLMGR_DR
PACKAGE BODY FLOWS_030100.WWV_FLOW_DATALOAD_XML
PACKAGE BODY MDSYS.SDO_OLS
PACKAGE BODY FLOWS_030000.WWV_FLOW_DATALOAD_XML
PACKAGE BODY FLOWS_030100.WWV_FLOW_XLIFF
PACKAGE BODY FLOWS_030000.WWV_FLOW_XLIFF
PACKAGE BODY EXFSYS.DBMS_RLMGR_DR
PACKAGE BODY XDB.DBMS_XSLPROCESSOR
PACKAGE BODY XDB.DBMS_XMLPARSER
PACKAGE BODY FLOWS_030100.WWV_FLOW_XLIFF
PACKAGE BODY XDB.DBMS_CSX_INT
PACKAGE BODY FLOWS_030000.WWV_FLOW_XLIFF
PACKAGE BODY EXFSYS.DBMS_RLMGR_DR
PACKAGE BODY XDB.DBMS_XDB
PACKAGE BODY XDB.DBMS_XDBRESOURCE
PACKAGE BODY XDB.DBMS_XMLDOM
PACKAGE XDB.DBMS_XSLPROCESSOR
PACKAGE XDB.DBMS_XMLPARSER
PACKAGE XDB.DBMS_XDBRESOURCE
PACKAGE BODY XDB.DBMS_XMLDOM
PACKAGE BODY XDB.DBMS_XMLINDEX
PACKAGE BODY XDB.DBMS_XMLPARSER
PACKAGE BODY XDB.DBMS_XMLPARSER
PACKAGE BODY XDB.DBMS_XMLSCHEMA
PACKAGE BODY XDB.DBMS_XMLSCHEMA
PACKAGE BODY XDB.DBMS_XMLSCHEMA_INT
PACKAGE BODY XDB.DBMS_XMLTRANSLATIONS
PACKAGE BODY XDB.DBMS_XSLPROCESSOR
PACKAGE BODY XDB.DBMS_XMLPARSER
PACKAGE BODY XDB.DBMS_CSX_INT
PACKAGE BODY XDB.DBMS_XMLDOM
PACKAGE BODY XDB.DBMS_XSLPROCESSOR
############# XML SCHEMAS #############
MDSYS has 4 registered.
EXFSYS has 2 registered.
ORDSYS has 17 registered.
XDB has 25 registered.
SYS has 43 registered.
############# Repository Resources #############
MDSYS has 9 resources.
EXFSYS has 3 resources.
ORDSYS has 20 resources.
XDB has 28 resources.
SYS has 12634 resources.
############# Network ACLs Configured #############
mail.4aps.be has network acls configured for ports 25 through 25
* has network acls configured for ports through
* has network acls configured for ports through
############# DBMS_EPG DAD USAGE #############
APEX
IMAGES

Hi Jules,
You need a user with XDBADMIN rights to access the WebDav. Once you have access, you can open the URL as webfolder (in IE).
Regards,
Christian

DB Upgrade+Migrate from 10.1 to 11.2 using IMPDP with network_link param

Dear all,
I would like to upgrade and migrate my 10.1.0.5 DB on old server to 11.2.0.2 on new server.
Here is the background info:
Old server:
OS : Redhat Linux AS 2.1
DB Version : 10.1.0.5 (32 bit)
No RAC
New Server:
OS : OEL 5.5
DB Version : 11.2.0.2
RAC
ASM
What I have done so far:
1. Create new clustered 11Gr2 DB on new server.
2. Pre-create tablespaces on new DB.
3. Migrate 10.1.0.5 to 11.2.0.2 using IMPDP.
impdp system/******* DIRECTORY=dump_file_dir NETWORK_LINK=DWH_DBLINK LOGFILE=log_file_dir:DWH_import_20110621.log FULL=Y SERVICE_NAME=dwhdb.xxx.xxx TABLE_EXISTS_ACTION=replace cluster=N exclude=statistics
4. After IMPDP complete, invalid objects and components are found, run utlrp.sql no help
SQL> select owner, count(*) from dba_objects where status = 'INVALID' group by owner;
OWNER COUNT(*)
WKSYS 16
PUBLIC 12
OLAPSYS 7
ODM 21
SYS 2
WMSYS 11
12 rows selected.
SQL> select comp_name, status, version from dba_registry;
COMP_NAME STATUS VERSION
OWB VALID 11.2.0.2.0
Oracle Application Express VALID 3.2.1.00.12
Oracle Enterprise Manager VALID 11.2.0.2.0
OLAP Catalog VALID 11.2.0.2.0
Spatial VALID 11.2.0.2.0
Oracle Multimedia VALID 11.2.0.2.0
Oracle XML Database VALID 11.2.0.2.0
Oracle Text VALID 11.2.0.2.0
Oracle Expression Filter VALID 11.2.0.2.0
Oracle Rules Manager VALID 11.2.0.2.0
Oracle Workspace Manager INVALID 11.2.0.2.0
Oracle Database Catalog Views VALID 11.2.0.2.0
Oracle Database Packages and Types INVALID 11.2.0.2.0
JServer JAVA Virtual Machine VALID 11.2.0.2.0
Oracle XDK VALID 11.2.0.2.0
Oracle Database Java Packages VALID 11.2.0.2.0
OLAP Analytic Workspace VALID 11.2.0.2.0
Oracle OLAP API VALID 11.2.0.2.0
Oracle Real Application Clusters VALID 11.2.0.2.0
19 rows selected.
5. Check SYS's invalid objects, e.g. DBA_OUTLINE_HINTS, after tracing the reason, find outln.ol$hints is replaced by 10.1.0.5 version. I think it is due to the IMPDP's "TABLE_EXISTS_ACTION=replace" parameter.
Others invalid objects like WMSYS.WM$ENV_VARS, also replaced by old version.
What should I do now?
Do I need to run upgrade script after DB migration using IMPDP?
Is the migration procedure correct?
Please advise
Thanks in advance

Hi,
It looks like you've messed up the Non User (Oracle default user) data and/or metadata i.e sys, system, wksys.
How many non Oracle default user do you have? and how big is the database? If you're using this method I'm assuming the data is not really big.
I personally will not do full export/ import across different version, its better to just export the non default Oracle user schema as you might ended up messed up the sys objects, etc
What you might do is
- drop the 11g database and start from beginning again but exclude Oracle default user e.g sys,system, etc
- or try run catupgrd.sql script (this will drop and recreate the objects), -this may or may not be fixing your invalid components
Cheers

OWB View validation??

Similar Messages

Maybe you are looking for