OracleCommandBuilder (with schema prefix)

Hi,
I'm using a simple SELECT command :
SELECT * FROM mySchema.myTable
Prior, I haven't use the schema and all has worked fine (with a CommandBuilder). Now I'm using the schema prefix and the generated SLQ for an update statment looks like :
UPDATE myTable set myAttr = ... where ...
The mySchema. is not used by the command builder to generate the update/insert/delete statment, so the table could not be found.
Any idea how to set the command builder that it will use the schema prefix ?
Thanks

This has been identified as a bug in the provider. The fix would be available in the next release.

Similar Messages

Problem naming table with schema prefix in Trigger

Hi,
When i try to compile the trigger having that body :
BEGIN
Insert into TechDb.DocumentTransfers(DocumentNumber, DocumentTypeID, StaffCodeFrom,
StaffCodeTo, TransferType, TransferDate)
values (:New.DocumentNumber, :New.DocumentTypeID, :New.StaffCode,
:New.StaffCode, :New.LastOperation, :New.DocumentDate);
END;
I get the following error :
Line # = 2 Column # = 4 Error Text = PLS-00201: identifier 'DOCUMENTTRANSFERS' must be declared
I noticed that the error disappears works if i don't need to prefix the DOCUMENTTRANFERS table with the schema name.
I am missing something ?
Thanks very much for your help.
Christian Moungou

Thanks John and Todd. It works exactly as you said.
But, does that mean i will have to directly grant the access right to all the users who will do the action which activates the trigger ?
Just to confirm : I assume that the user who executes the trigger is the user who does the action that activates the trigger ?
Christian

DatabaseProcedure with return type prefixed with schema name

Hi (Paco)
I have a question about the DatabaseProcedure class. We are using Oracle proxy users for our database connections.
Everything is accessed via a database role that are granted to the logged on user. All our database objects, tables etc are protected with this database role.
When I want to call a database function/procedure I need to add the schema name as a prefix to the custom database object that we uses for parameters/return types.
So far so good. I can also define a parameter prefixed with schema name via the DatabaseProcedure.registerArrayType ...
But when I try to define a function call that uses this parameter I get an error saying "Declaration is not valid".
The problem is located to the PROCEDURE_DEFINITION regular pattern:
private static final Pattern PROCEDURE_DEFINITION = Pattern.compile("\\s* (FUNCTION|PROCEDURE) \\s+ ([\\w.$]+) \\s* (?:\$(.*?)\$)? \\s* (?:RETURN\\s+(\\w+))? \\s* ;? \\s*", CASE_INSENSITIVE | COMMENTS | DOTALL); The return type cannot be prefixed with the schema name.
Any good suggestions or workarounds?!
I actually did change the pattern runtime via reflection to make it work - but I really don't like this solution in the long run!
/Torben
Edited by: Zonic on 2013-05-07 10:52

Hi Torben,
I think I have a workaround for the issue that might work for you. If you look at the source of DatabaseProcedure.registerArrayType you find that it actually calls DatabaseProcedure.registerCustomParamType.
public static void registerArrayType(String name)
registerCustomParamType(name, Types.ARRAY, Array.getORADataFactory(), name);
}As a workaround you could replace your calls to DatabaseProcedure.registerArrayType with calls to DatabaseProcedure.registerCustomParamType as follows.
// Instead of DatabaseProcedure.registerArrayType("NAME.WITH.DOTS") call:
DatabaseProcedure.registerCustomParamType("anyNameWithoutDots", Types.ARRAY, Array.getORADataFactory(), "NAME.WITH.DOTS"); // Don't forget to use uppercase here.
DatabaseProcedure dp = DatabaseProcedure.define("procedure my.procedure(param1 in out anyNameWithoutDots)");
DatabaseProcedure.ParamType type = dp.getParamDef(0).getType();
System.out.println(type.getName() + " is " + type.getTypeName()); // ANYNAMEWITHOUTDOTS is NAME.WITH.DOTSThis way you don't have to use the "illegal" name in the DatabaseProcedure definition.
Regards,
Paco van der Linden

Generate DDL with schema name prefix

Hi All
We are trying to generate DDL with the schema prefix on all statements.
eg. CREATE schema_name.table_name
Is it possible to do this with Designer 6i/9i or even 10g? I guess it might a server generator preference setting.
Thanks
Kathy

Well dbms_metadata.get_ddl will generate the ddl script with username by default if you dont want you can try your own script. Check the sample function which create to fix that.
Hope this helps.
SRI>set long 1000000
SRI>create or replace function aaa(nstr varchar2,nuser varchar2) return varchar2 is
2 begin
3 return replace(nstr,chr(34)||nuser||chr(34)||'.','');
4 end;
5 /
function created
SRI>select dbms_metadata.get_ddl('TABLE','DEPT') from dual
DBMS_METADATA.GET_DDL('TABLE','DEPT')
CREATE TABLE "SCOTT"."DEPT"
( "DEPTNO" NUMBER(2,0),
"DNAME" VARCHAR2(14),
"LOC" VARCHAR2(13)
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "TOOLS"
SRI>select aaa(dbms_metadata.get_ddl('TABLE','DEPT'),'SCOTT') from dual;
AAA(DBMS_METADATA.GET_DDL('TABLE','DEPT'),'SCOTT')
CREATE TABLE "DEPT"
( "DEPTNO" NUMBER(2,0),
"DNAME" VARCHAR2(14),
"LOC" VARCHAR2(13)
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "TOOLS"
-Sri

Calling table without schema prefix.

I have a task to upgrade a form 6 and oracle 8 based system to form 6i and database 9ii.
I notice in legacy Forms that other schema objects has been called in Select and Update statements without schema prefix.. like select * from tablename instead of select * from schemaName.tbalename
Forms are not able to compile without schema prefix before table name.
Is it happened in 6i or some thing is missing at database side

ORA-600 are internal errors; you'd need to contact oracle support for it. Before you log a SR with support you might give the Ora-600 lookup tool a chance (metalink note 153788.1).
But as Forms 6i and database 9i are rather outdated you might have a good chance that "update to a supported version" is the answer you get from support.
cheers

Removing schema prefix from DDL statements

When I do a change via sql developer, such as adding/dropping a field or table, etc... I need to send the change as a SQL script to my DBA (so it could be sent with our next upgrade to customers, etc).
But, the changes are always prefixed by the schema owner. How can I remove this? For example, if I add a field called: B to table: A, which is under schema O, the sql will look like this:
alter table O.A add (B);
I don't want the "O." to be in there by default. IMO, it is "stupid" for SQL Developer to do this.
My connection profile is to login as user "O".
I do see an option:
Preferences, Database, ObjectViewer Parameters: Show Schema
I un-check this box, because it does make one thing better: it makes it if I goto the "SQL" tab of a table i'm looking at, the sql to create the table won't have the schema prefix, which I think is the "correct" behaviour.
Is there anyway to "turn off schema prefix" for my "alters" ?

On the connections tab...
I expand TAbles
I highlight the table i want to add to.
I click Actions
I click Columns, Add
I proceed with entering the column via the GUI.
There's a tab called "SQL" that writes the SQL for whatever i'm doing. I want to be able to take this sql and send to my DBA, but I don't want it to be prefixed by the schema owner.

Error message while executing international payroll with schema x000

Dear Team,
I am getting the below error message while running international payroll with schema x000.
   "Jump from DAYPR to detailed log
   Incorrect generation of wage types"
Request forum members to help me on the same.
Thank you,
Srinivas

Hi,
Thank you for the reply please find below i reviewed all the below tables please gothrough and advice me if any i missed out.
1)     T555E-Message Descriptions----
2) T551C-Period work schedule evaluation---
Grpg        Period ws     Description     Start Date      End Date      Cntg Class
   01     PWTC         Period WS     01.01.1990      31.12.9999     1
3) V_551C_B-Valuation class for Periodic work schedule
Grpg Period ws Description     start Date       End Date       Val.Classfor PWS
01      PWTC      Period WS       01.01.1990    31.12.9999       1
4) V_t508A-Work schedule rule
ESG    ES grpg for ws     Holiday      Text      PSG   WSrule    St Date          End Date
2        Salaried Employee   TCD             TC         01     TCWR    01.01.1900   31.12.9999
5) V_001P_H-Personnel Subarea grouping for Time Recording
Personnel area Personnel Area Text Personnel Subarea Pers.Subarea Ps Group
1100                 JEDDAH            1110              MAIN OFFICE           01
6) V_T555Z- Time type Determination
Can you advice me on this what I need to maintain here
7) V_T510S-Time wage type selection rule
Tm.WT Dy Grpg          No                                                   Wagetype Wage Type Long Text
54       01               001                                              1010            Basic Pay
Regards,
Srinivas

Xml validation with schema, unbounded and any order of elements

Hi
I want to validate a xml file the user creates. I am currently using schema to do this. However there needs to be the possibility of a totally random mix of three different types of elements in a parent element. I couldn't find out how to do this, maybe it is not possible with schema? I thought I could look at the error message generated and ignore it if it was caused by one of the three elements mentioned above, but while the error message generated says which element is expected, it does not say which element caused the error.
Thanks in advance for any help.

Ruskin wrote:
However there needs to be the possibility of a totally random mix of three different types of elements in a parent element. Can you take your example to make it more clear? Does all three elements mutually exclusive?

SQL Dev converts MS SQL to Oracle - issue with numeric prefix column name

Hi,
We're working on migrating MS SQL data into Oracle 10g. An issue we encountered is that some of MS SQL's tables have column names with numeric prefix like 1Q07, 2Q07, ..., 4Q08, and so on. The converted model as well as script can be created. But one thing I notice is that SQL Dev appends a prefix "A" for column names with numeric prefix. This makes sense because Oracle does not allow a column with number. But somehow this does not work with only 4Q
1Q04 => A1Q01
2Q07 => A2Q07
3Q08 => A3Q08
4Q08 => 4Q08 ???
Why? Any place in the tool where I can override this?
Obviously I can manually modify column name 4Q08 to A4Q08 in the script. But by doing this when moving data, it would fail because tool has no knowledge of updated column name.
Thanks in advance.

Hi ittichai,
In <repository>.MIGRATION_TRANSFORMER body
FUNCTION first_char_check(p_work NVARCHAR2) RETURN NVARCHAR2
v_allowed := C_DISALLOWED_CHARS || '012356789_$';
should be
v_allowed := C_DISALLOWED_CHARS || '0123456789_$';
If you make this change and convert the 4Q08 will be
A4Q08 is expected, without any manual rename.
-Turloch
Message was edited by:
Turloch O'Tierney

SAX Parser Validation with Schemas (C, C++ and JAVA)

We are currently using the Oracle XML Parser for C to parse and validate XML data using the SAX parser interface with validation turned on. We currently define our XML with a DTD, but would like to switch to schemas. However, the Oracle XML Parser 9.2.0.3.0 (C) only validates against a DTD, not a schema when using the SAX interface. Are there plans to add schema validation as an option? If so, when would this be available? Also, the same limitation appears to be true for C++ and JAVA. When will any of these provide SAX parsing with schema validation?
Thanks!
John

Will get back to you after checked with development team...

Training an SVM on table with schema flexibility fails

Dear colleagues,
I'm trying to train a Support Vector Machine on a table with schema flexibility.
On a small test table with only a couple of columns both the training and the prediction using the PAL libraries work fine. However, on my large sparse table with more than 1000 columns and "schema flexibility" set at creation time, I constantly run into the following error:
Could not execute 'CALL SYSTEM.AFL_WRAPPER_GENERATOR ('PAL_SV', 'AFLPAL', 'SVMTRAIN', PAL_SV_SIGNATURE)' in 30 ms 529 µs .
SAP DBTech JDBC: [423]: AFL error: [423] "SYSTEM"."AFL_WRAPPER_GENERATOR": line 32 col 1 (at pos 1346): [423] (range 3) AFL error exception: AFL error: registration finished with errors, see indexserver trace
The indexserver trace gives me something strange like:
AFLPM_SQLDriverObj.cpp(02439) : aflpm_creator : direction must be in or out
As far as I see it, all parameters are fine, though.
Is there a limitation that does not allow PAL functions to be executed on tables with schema flexibility? I suspect so, because I'm running into similar problems with the SUBSTITUTE_MISSING_VALUES function.
Thanks for any help,
Daniel

Hey there,
isn't there anyone who came across this issue? I'd love to know if this is a known technical limitation with tables that use the "schema flexibility" or rather a bug. In the former case, can anyone suggest a workaround?
I'd be grateful for any help or any pointer to further documentation.
Best,
Daniel

OMWB schema prefix (MS SQL Server to Oracle database migration)

I made automatical migration + some manual changes (pipelined functions) to migrate MS SQL 2000 database to Oracle 9i. Still one issue remains which requires lot of manual conversion : Names of the tables in views after automatic migration doesn't contain schema prefix and it doesn't compile on destination database.
My question is: Is there any way to add schema prefix to table names in views automatically during migration process ?

Two things here.
The omwb will login to Oracle and create the views in the schema where they will be stored, hence not needing the schema appended.
If the views are on other schemas than the one being installed into, then yes, there may be some manual edits to do to the table names in the views. This is not configurable today.

OMWB schema prefix (MS SQL Server to Oracle database conversion)

I made automatical conversion + some manual changes (pipelined functions) to migrate MS SQL 2000 database to Oracle 9i. Still one issue remains which requires lot of manual conversion : Names of the tables in views after automatic conversion doesn't contain schema prefix and it doesn't compile on destination database.
My question is: Is there any way to add schema prefix to table names in views automatically during migration process ?

Hi Marcin,
See my post in the OMWB forum
Thanks
BArry

Create a wsdl file - with schemas inline - in JDeveloper

Hi,
We are trying to create a wsdl file using schemas in jdeveloper 11.1.1.3. We could generate the wsdl file using options available in jdeveloper, but the wsdl generated contains <types> element that has schemas referenced by only an "import" statement as below.
<types>
<xsd:schema>
<xsd:import schemaLocation="../../../Test.xsd" namespace="http://www.openuri.org"/>
</xsd:schema>
</types>
But, I would like get the schemas inlined or embedded within the wsdl instead of just an import statement.. This helps me in using the wsdl anywhere (creating webservices or use in my applications or give it to some one to use) without worrying about the actual schema definition files. The <types> element within the wsdl must have the schemas embedded, something like below.
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://testWSDLproject/type" elementFormDefault="qualified">
<xsd:element name="testIn">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="value" type="xsd:integer"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
Is there any way forward, with the Jdeveloper to create wsdl files with schemas inline ?

Hi Vohra,
The schema snippet pasted previously was just a sample.
In actual, there are mulitple cross referencing xsd files that must be embedded within my wsdl file. Sometimes, such manual editing of wsdl (embedding so many schema definitions) is prone to errors.
If there is an option in Jdeveloper which automatically does this embedding for us, then it becomes more handy. Have you come across any such options ?

Multi tenancy with schema per tenant

Hello,
I am tryign to run multi tenancy with schema per tenant. It seems to work good when tenant ID is set in XML as a property for persistance unit.
But I need to set tenant in code. Is that possible? How?
I found this article:
codecrafters.blogspot.it/2013/03/multi-tenant-cloud-applications-with.html
So I tried to set it in doBegin method in custom transaction manager. But that doesn't work. I guess relation descriptors aren't updated right.
I could provide more info with exception stack also but first... have I pick the right approach?
Thanks!
Martin

UPDATE 26.6.2015: This isn't completelly right solution. Read also comments below or go to my article at http://www.mafospace.com/articles/multi-tenancy-with-eclipselink-and-inherited-entities
I've solved it finally. Maybe it will be helpful for someone. I've done that in similar way as described in article I linked in first post. Through custom transaction manager.
import org.eclipse.persistence.config.PersistenceUnitProperties;
import org.eclipse.persistence.internal.jpa.EntityManagerImpl;
import org.eclipse.persistence.sessions.coordination.MetadataRefreshListener;
import org.eclipse.persistence.sessions.server.ServerSession;
import org.springframework.orm.jpa.JpaTransactionManager;
import sk.bantip.hotel.server.security.SecurityHelper;
import javax.persistence.EntityManager;
import java.util.HashMap;
import java.util.Map;
public class MultiTenantJpaTransactionManager extends JpaTransactionManager {
* NOTE:
* Maybe it would be also possible to replace existing entityManager in transaction with new but it
* isn't a good idea because of rollback and other problems.
* So when new tenant is required always start new transaction for it.
@Override
protected javax.persistence.EntityManager createEntityManagerForTransaction() {
EntityManager em = super.createEntityManagerForTransaction();
boolean refreshed = false;
String actualTenant = null;
ServerSession ss = ((EntityManagerImpl) em.getDelegate()).getServerSession();
Map sessionProp = ss.getProperties();
actualTenant = (String) sessionProp.get(PersistenceUnitProperties.MULTITENANT_PROPERTY_DEFAULT);
// don't run it if tenant didn't change
// it should be quite faster then
if ((actualTenant == null && SecurityHelper.getActiveTenantSchema() != null) ||
(actualTenant != null && !actualTenant.equals(SecurityHelper.getActiveTenantSchema()))) {
// set new tenant as property for actual session
// while refreshing metadata it will be used from actual session for new session
sessionProp.put(PersistenceUnitProperties.MULTITENANT_PROPERTY_DEFAULT, SecurityHelper.getActiveTenantSchema());
MetadataRefreshListener mrl = ((EntityManagerImpl) em.getDelegate()).getServerSession().getRefreshMetadataListener();
// metadata refresh listener is empty if it was already run for actual transaction (same entity manager)
// because it is placed in createEntityManagerForTransaction now this shouldn't happen but to be sure...
if (mrl != null) {
Map<String, Object> prop = new HashMap<String, Object>();
// metadata will be refreshed for next created entity manager
mrl.triggerMetadataRefresh(prop);
refreshed = true;
// if metadata for "old" entity manager wasn't refreshed we don't need to create a new one
return refreshed ? super.createEntityManagerForTransaction() : em;
Everything seems to work except inheritance with strategy type JOINED now. To fix that use customizer.
import org.eclipse.persistence.annotations.TenantTableDiscriminatorType;
import org.eclipse.persistence.config.DescriptorCustomizer;
import org.eclipse.persistence.descriptors.ClassDescriptor;
import org.eclipse.persistence.descriptors.TablePerMultitenantPolicy;
* For some reason when using table per tenant with schema discriminator isn't set good for child
* entities with inheritance JOINED strategy. It stay as SUFFIX and therefore it doesn't work.
public class InheritanceJoinedMTFixCustomizer implements DescriptorCustomizer {
@Override
public void customize(ClassDescriptor descriptor) throws Exception {
// set discriminator to SCHEMA
((TablePerMultitenantPolicy) descriptor.getMultitenantPolicy())
.setTenantTableDiscriminatorType(TenantTableDiscriminatorType.SCHEMA);
And in child entities use it like this:
@Customizer(InheritanceJoinedMTFixCustomizer.class)
public class Person extends Contact {

OracleCommandBuilder (with schema prefix)

Similar Messages

Maybe you are looking for