Question about import database pk, fk

Hi
I want to ask a question about imported database. I imported database and I noticed tables doesnt have Primary key or foreign key. They havent relation between eachs. Why can this occured ?
is it about import or another something?

yeah ı am surprised none of tables have pk or fk ..
but ı want to show you http://i51.tinypic.com/2hedc9d.jpg
what is blue shapes in there ?
can be foerign keys ?

Similar Messages

Basic question about importing wma files

Hi, I have a basic question about importing wma files. I ripped some cd's on a Mindows computer using Media Player, but now want to copy them to my Mac and use them in iTunes on my Mac. when I use Import in iTunes, nothing happens and I cant even seem to copy them one by one using the Music folder.
Can someone help me?
thanks
eMac Mac OS X (10.4.4)

iTunes for Mac doesn't support .wma files.
If you can use a PC to convert them, you can use one of many freeware applications. Google for 'wma to mp3'.
For the Mac there's the shareware program EasyWMA that can convert them.
Hope this helps.
M
17' iMac fp 800 MHz 768 MB RAM Mac OS X (10.3.9) Several ext. HD (backup and data)

Few questions about upgrading database

Hi everyone,
greetings of the day
I have few questions about the upgrading database,
In export and import mode
1.can we have new name for the target database,
2.I think we need to create tablespaces ,do we need to create users as well
3.If we are upgrading from 9i to 10g database ,any activity to be perfromed other than creating a new sysaux tablespace
4.How come we get consistent export
In DBUA mode ( in the same machine only)
1.Do we need shutdown / startup restrict the database
2.How can we move the files to the new location
3.Can we change db_name of the database
4.Can we use the old database as well
In manual upgration using catupgrd scripts
1.Can we rename the db_name
2.can we use old database as well
3.how to move the database files to the new location
4.can we perform this kind of upgrade on a different server
5.when we startup upgrade in the new home ,how it identifies the old database in-order to upgrade the old one
Thanks

udayjampani wrote:
Hi everyone,
greetings of the day
Pl post details of source and target database versions, along with your OS details.
I have few questions about the upgrading database,
In export and import mode
1.can we have new name for the target database,Yes.
2.I think we need to create tablespaces ,do we need to create users as wellYou can create users, but it is not necessary. You need to pre-create tablespaces only if their characteristics/locations on the target are different than on the source.
3.If we are upgrading from 9i to 10g database ,any activity to be perfromed other than thisNot that I am aware of - see the steps in the Upgrade Guide - http://docs.oracle.com/cd/B19306_01/server.102/b14238/expimp.htm
4.How come we get consistent export wetherEnsure the database is started in restricted mode, so users will not be able to access the database during the export.
>
In DBUA mode ( in the same machine only)
1.Do we need shutdown / startup restrict the databaseNo - DBUA will do this automatically for you.
2.How can we move the files to the new locationYou can after the upgrade move the datafiles to wherever you want - use the ALTER DATABASE RENAME DATAFILE (http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_1004.htm#i2082829) command.
3.Can we change db_name of the databaseI do not believe this is possible with DBUA.
4.Can we use the old database as wellNo - the database will be upgraded by DBUA - there is no "old" database.
>
>
In manual upgration using catupgrd scripts
1.Can we rename the db_nameYes.
2.can we use old database as wellNo - the scripts will upgrade the database - there is no "old" database.
3.how to move the database files to the new locationSee above.
4.can we perform this kind of upgrade on a different serverPl elaborate on what you mean by this. You can copy the existing database to a different server (assuming compatible OS) and upgrade it there.
>
>
ThanksHTH
Srini

Some questions about importing HTML files

Hi, folks
Let's suppose we want to import a pack of HTML files formatted in HTML5 wit's it's CSS into a double-oriented folio. A couple or three questions about that, please:
1. Is there a limit for a reasonable quantity of HTML files I can import into a folio? I mean.. 100 would be way too much, for instance?
2. These HTML files could be navigated and referenced from inside TOC-pages made in InDesign,right? (navto://..., I gues?)
2. Will it be possible, by means of HTML adaptative design techniques, to treat both orientations (vertical and horizontal) as different viewports or screen sizes so that the design adapts for instance the column width with its CSS?
3. That said, will the InDesign final app. respect that adaptative CSS rules?
I am asking this because we are looking for a way to inject big quantities of content with a very similar design into our application in a really fast and automatizable way and I have the suspicion* that importing HTML5 preformated CSS files could be the a very good and simple alternative to importing XML into InDesign templates as we start out content as tagged almost-html files.
Thanks a lot
Gustavo Sánchez (Posting from Madrid)

I assume you are asking about using HTML articles.
1. There is no limit beyond simply keeping things reasonable.
2. Yes. Just use navto://articlename
3. Yes. I've used min-width of 768 and max width of 1024 to control it.
4. InDesign does not enter into any of this with the exception of using the folio builder panel. Everything else is done in Dreamweaver or whatever program you decide to use for the article.
If you want to restrict the HTML articles to one orientation or the other, use the _h and _v suffixes.
Bob

A Question about LV Database Connectivity Toolkit

Hello everyone!
I have a question about using LabVIEW DataBase Connectivity Toolkit 1.0.2 that eagerly needs your help. I don't know how to programmaticlly create a new Microsoft Access(.mdb)file (Not a new table in a existing Database)using LabVIEW Database Connectivity Toolkit1.0.2. As you know, usually we can set up the connection by creating a Universal Data Link (.udl) file and inputting the path to the DB Tools Open Connec VI in the LabVIEW DataBase Connectivity Toolkit. However, searching a table within an existing database containing a great many tables is a toilfulif job. If I want to use a new DataBase file with the date and time string as its name to log my acquisition data in each measurement process, how to do? I am sure someone of you must can resolve my question, and thanks very much for your help.

I don't know what your real design considerations are here but, from I understand from your post, this is a really bad way to go about the process of logging data -- IF you want to be able to do significant ad hoc or stored procedures analyses after it has been collected. Using separate MDB files for data that ONLY differs by one field (namely that date) is not the most efficient way to organize it. What would be much more efficient would a joined table including the date and a reference ID of some sort for the various measurements that were done. That way your stored procedures for looking at ALL measurements of type X would be very simple going across ALL dates. Making such a comparison across multiple MDB files is a much more challenging process AND doing the original data collection in that way doesn't really gain you anything.
Generally, if something is difficult to do in the DCT (Database Connectivity Toolkit) it's because it's a "not good thing" to do within MDBs. I know that others probably disagree with that but I've worked with Access since it's initial release and other RDBMs prior to that both through compiled tools, Unix scripts, etc. You may, of course, still choose to proceed in the way you've described and that may work excellently for you.

Basic question about Flashback Database

Hi,
I have a very generic question about using Flashback Database.
On my testing systems, for performance testing and simulation purposes, I want to create a guaranteed restore point so I can test impact on batch when code change releases are done, before deployment in production. My confusion is with respect to redo logs, as summarized in the questions below:
1. Is it possible to change redo log files, when a guaranteed restore point has been configured?
2. If yes, will the Flashback to restore point, also change the size of the redo logs?
I could not find anything in the docs about this....hence my question....
Appreciate your time taken in responding to these questions....
Regards.

HI,
donneskold wrote:
Hi,
I have a very generic question about using Flashback Database.
On my testing systems, for performance testing and simulation purposes, I want to create a guaranteed restore point so I can test impact on batch when code change releases are done, before deployment in production. My confusion is with respect to redo logs, as summarized in the questions below:
1. Is it possible to change redo log files, when a guaranteed restore point has been configured?
1) Yes it is possible.
2. If yes, will the Flashback to restore point, also change the size of the redo logs?
2) It will not change the size of redo log file. Cannot resize a redo log file..
I could not find anything in the docs about this....hence my question....
Appreciate your time taken in responding to these questions....
Regards.
Thank you

Question about Oracle Database 11g: Program with PL/SQL

Hello,
I've read that:
This course is a combination of Oracle Database 11g: PL/SQL Fundamentals and Oracle Database 11g: Develop PL/SQL Program Units courses.
In order to preparing for this exam, i should read the student guide, so there are 4 pdf files. One is Oracle Database 11g: PL/SQL Fundamentals, and the other 3 are regarding to Oracle Database 11g: Develop PL/SQL Program Units (volume I, II and III). My question is, regarding to this last one (Oracle Database 11g: Develop PL/SQL Program Units), which volume should i read? I saw that volume I has 400+ pages, and the IIIrd ~80.
Which document should i read? What's the difference between them?
Thanks!

Passing the exam and becoming certified are not a matter of simply reading a book or taking a training class. While books and classroom materials as well as in-class training are all important steps in preparing for an exam, experience and research are just as important. I cannot tell you that there are 53 questions on the exam and every single question maps directly back to page 13, paragraph 3 in XX book. However, If you have the classroom material, and you have the list of exam topics, you should be able to find most of the information you need. In some cases, if you are not completely familiar with a specific topic, or you don't feel like the information in the book gives you all the information you need, you may need to do a little additional research. This is all part of preparing for an exam. This process is what makes you successful as a certified professional.
Your focus seems to be solely on the course materials that you have and what volumes and chapters you should read. I'm trying to give you a different perspective - preparing for an exam is not necessarily about taking one course or reading one book and being ready. You need to review the exam topics and be sure that you are familiar with each topic.
Regards,
Brandye Barrington

Question about B1if-Database in SQL-Mgmt-Studio

Hello,
We have made some changes in the configuration in SLD.
We made some more Di-Proxy-Ports and then made Proxygroups for the Databases.
Nearly every half hour, in SQL-Mgmt Studio we can see this "task" ?
During the time, this task is online, the Queue-Monitor collects all Jobs... but not more.
After this Job has finished... B1i begins to work up the jobs.
Can anyone tell me something about "Rollback Transac" in B1if-Database ?
Thanks
Markus

Passing the exam and becoming certified are not a matter of simply reading a book or taking a training class. While books and classroom materials as well as in-class training are all important steps in preparing for an exam, experience and research are just as important. I cannot tell you that there are 53 questions on the exam and every single question maps directly back to page 13, paragraph 3 in XX book. However, If you have the classroom material, and you have the list of exam topics, you should be able to find most of the information you need. In some cases, if you are not completely familiar with a specific topic, or you don't feel like the information in the book gives you all the information you need, you may need to do a little additional research. This is all part of preparing for an exam. This process is what makes you successful as a certified professional.
Your focus seems to be solely on the course materials that you have and what volumes and chapters you should read. I'm trying to give you a different perspective - preparing for an exam is not necessarily about taking one course or reading one book and being ready. You need to review the exam topics and be sure that you are familiar with each topic.
Regards,
Brandye Barrington

Basic question about import

I need to import an already existing user from a dmp file.
I am not sure if I must drop and recreate the user before importing or the import would drop all not existing objects, create the new ones, modify those that are different, insert new records, delete those not in the dmp file and update the different ones.
Thanks in advance.

Unfortunately the advice from the other poster is
just plain wrong.I wouldn't classify it as "plain wrong", "not accurate" yes maybe, but not wrong.
The OP's question was that he needs to import already existing user with existing objects.
Quoting Oracle's online Documentation of Oracle Utilities, Import's IGNORE parameter:
IGNORE
Default: n
Specifies how object creation errors should be handled. If you accept the default, IGNORE=n, Import logs or displays object creation errors before continuing.
If you specify IGNORE=y, Import overlooks object creation errors when it attempts to create database objects, and continues without reporting the errors.
Note that only object creation errors are ignored; other errors, such as operating system, database, and SQL errors, are not ignored and may cause processing to stop.
In situations where multiple refreshes from a single export file are done with IGNORE=y, certain objects can be created multiple times (although they will have unique system-defined names). You can prevent this for certain objects (for example, constraints) by doing an import with CONSTRAINTS=n. If you do a full import with CONSTRAINTS=n, no constraints for any tables are imported.
If a table already exists and IGNORE=y, then rows are imported into existing tables without any errors or messages being given. You might want to import data into tables that already exist in order to use new storage parameters or because you have already created the table in a cluster.
If a table already exists and IGNORE=n, then errors are reported and the table is skipped with no rows inserted. Also, objects dependent on tables, such as indexes, grants, and constraints, will not be created.
Tony

Question about import in archive log mode

Hello.
I am a developer, I have ordered to write a script that makes the import of a schema of a database (release 9.2.0.7). That import will be done once a day. I have seen that in my development environment the import creates 54 archivers files (10M aprox. each), that means more that half a Gb a day, it seems too much to me.
I cannot see why all those archivers can be useful. Would a good way of proceeding the following?
1. Forcing an archiver just before the import (I do not know how to do that) so that a backup could be done to the state before the import.
2. Disabling archive log mode during the import and enabling it just after the import (I do not know how to do that).
3. Forcing a new archiver just after the import (I do not know how to do that).
Thanks in advance.

540M is not that much.
One would question why you need to import every day,
there must be better ways to do this.
The three steps you propose look like an awful
scenario, as it would require the database to switch
from archivelog to noarchivelog and vice versa.
This would require the database to close twice a
day.
The scenario is also incomplete as one would need to
take a backup after the import
If you can convince your DBA to close the database
twice a day, he should write the script, which he can
easily derive from the docs.
But likely he will visit Billy Verreynne to borrow
his lead pipe, and rightly so ;)
Sybrand Bakker
Senior Oracle DBAThanks for the answer.
A few things:
- Sorry for my ignorance, I have no experience in database backups, I do not understand why I need to backup just after the import.
- That database is not critical, it is just for a team who will test on that database several applications, so the database will only need to be open during the office schedule.
- I have no dba. The client has a dba for several databases but I have no contact with him/her nor my boss has.

Question About Import Transport_Tablespace

I went through import transport_tablespace help
there writen in compitable heading that source and target hardware must be same
my question is if i run export command on pentium III and import on Pentium4 will it not work
and 2nd question is in source computer my tablespace's datafile location is e:\oracle\ora92\database\' and i copy datafiles on other location on target computer let's say c:\oracle\ora\database' will it work..

Hi,
What are your command exp and imp ?
All info for imp transportable_tablespace here http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch02.htm#1006719
All info for exp transportable_tablespace here
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch01.htm#1006961
Nicolas.

Some questions about my database access bean

The following is a bean (minus imports) that access a database and populates several "articles" and then returns a set of them. pretty plain really.
The bean is modified from here to add exception cactching and 'fix' other problems along the way.
http://forum.java.sun.com/thread.jspa?threadID=727979 (thanks evnafets)
The results list is genericified(!) to avoif unchecked calls (casting) in this line result.add(article);
public class dataAccess {
    public List getNewsResults() throws NamingException{
        Context initContext = new InitialContext();
        Context envContext = (Context) initContext.lookup("java:/comp/env");
        DataSource ds = (DataSource) envContext.lookup("jdbc/mySite");
        Connection conn = null;
        Statement stmt = null;
        ResultSet rs = null;
        List<newsArticleBean> result = new ArrayList<newsArticleBean>();
        try {
            String sql = "SELECT * FROM news, users WHERE news.user = users.username";
            conn = ds.getConnection();
            stmt = conn.createStatement();
            rs = stmt.executeQuery(sql);
            stmt.execute();
            while (rs.next()) {
                newsArticleBean article = new newsArticleBean();
                article.setTitle(rs.getString("title"));
                article.setAuthor(rs.getString("author"));
                article.setEmail(rs.getString("email"));
                article.setNews(rs.getString("news"));
                article.setPictureURL(rs.getString("pictureURL"));
                article.setDate(rs.getDate("date"));
                article.setTime(rs.getTime("time"));
                result.add(article);
        } catch (SQLException e) {
            //error message goes here
        finally {
            try {
                if (rs != null) rs.close();
            } catch (Exception e) {
                //error message goes here
            try {
                if (stmt != null) stmt.close();
            } catch (Exception e) {
                //error message goes here
            try {
                if (conn != null) conn.close();
            } catch (Exception e) {
                //error message goes here
    return result;
}Some questions that would be of great help if answered:
Im not too sure what a context does or what im doing with it here. My current understanding is that it allows concurrent access of the database.
        Context initContext = new InitialContext();
        Context envContext = (Context) initContext.lookup("java:/comp/env");
        DataSource ds = (DataSource) envContext.lookup("jdbc/mySite");This section im having trouble with too.
As I see it:
I set what my sql query will be;
get a connection @ conn
now im not too sure what stmt is getting, is it getting ready to send the query.
stmt does not have an executeQuery() method, so im never actually sure when the sql query gets sent to the database. I have subbed with execute() but it does not take any arguments so the problem of not sending anything remains.
            String sql = "SELECT * FROM news, users WHERE news.user = users.username";
            conn = ds.getConnection();
            stmt = conn.createStatement();
            rs = stmt.executeQuery(sql);Any help greatly appreciated.

Some questions that would be of great help if
answered:
Im not too sure what a context does or what im doing
with it here. My current understanding is that it
allows concurrent access of the database.
Context initContext = new InitialContext();
Context envContext = (Context)
Context) initContext.lookup("java:/comp/env");
DataSource ds = (DataSource)
aSource) envContext.lookup("jdbc/mySite");
Nops, it has nothing to do with concurrent access. You use tomcat to set up a Connection Pool. This causes the tomcat server to create a pool of reusable connections on startup. The connection pool (or set of Connection objects) are given a name and the server binds the set of objects to this name in a 'registry'.
From the code, you use jndi to access the Connections from the pooled objects. While doing so, you have to provide the jndi name against which this object pool is bound to.
You'll be more clear when you read the fllowing resources.
http://java.sun.com/products/jndi/
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
>
This section im having trouble with too.
As I see it:
I set what my sql query will be;
get a connection @ conn
now im not too sure what stmt is getting, is it
getting ready to send the query.Yes something of that sort - basically it provides you a wrapper which can accept your query, use the connection object to access the db, execute the query and return a result set.
stmt does not have an executeQuery() method, so im
never actually sure when the sql query gets sent to
the database.er....it has and that's what you use in your code. (http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Statement.html#executeQuery(java.lang.String))
I have subbed with execute() but it
does not take any arguments so the problem of not
sending anything remains.Hmmm....the execute() method is for a different purpose and it does accept arguments (http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Statement.html#execute(java.lang.String))
>
            String sql = "SELECT * FROM news,
users WHERE news.user = users.username";
conn = ds.getConnection();
stmt = conn.createStatement();
rs = stmt.executeQuery(sql);Any help greatly appreciated.ram.

Question about using database links in Forms 10g

I have a form that uses a database link for the "Query Data Source Name," i.e. it is set to some_view@some_db_link
For some reason when I run a query using the DB link the query takes approximately 30 seconds. When I remove the link and go local the query takes about one second. Has anybody observed and addressed this issue before (without going local of course)?
Thanks,
Thomas

Let me first say that it is never a good idea to use a db link in the data source. It is better to create a synonym in the database and use this as the data source. If the db link changes, you only have to do this in the database, without recompiling forms.
create synonym some_view for some_view@some_db_link
This may already solve your problem. If not, than see if the query is also slow in sqlplus. You may have a problem in your connection between the two databases.

Question about imported file

Hi,
I was taking a look to the tutorial provided by the otn web site about TopLink and I saw that we have to import the source.jar file.
I'm working with JBuilder and I have imported as a library toplink.jar, antlr.jar and xerces.jar and it works fine. Do I really need to also import source.jar and/or other .jar?

I would presume that the source.jar would only be needed in IDEs for parsing the source for code completion and Javadoc. Most newer IDEs are pretty good at parsing the .class files for most of the info though. So I don't think its really needed.
Darren

Stupid question about import/export

Hi All,
i'm banging my head against the wall :) :)
i have one database (oracle 10g) , the database is called ORAPD
in this database lives a user called WFAT
ORAPD -- WFAT
now i create 3 another users: WFATG , WFAUTOG, WFPATG
Now i want to import all data, objects, index,sequences etc from WFAT to each one of the other 3 users
ORAPD -- WFAT
-- WFATG (new user with objects from wfat)
-- WFAUTOG (new user with objects from wfat)
-- WFPATG (new user with objects from wfat)
this is want i've done.
export wfat objects, connected with user system with expdp
import wfaobjects to each one of the new 3 users with impdp , remapping schemas and tablespaces
f:\impdp system/passwordXXX schemas=wfat remap_schema=wfat:wfautog remap_ta
blespace=tbs_wfatg_tab:tbs_wfautog_tab remap_tablespace=tbs_wfatg_idx:tbs_wfauto
g_idx remap_tablespace=tbs_wfatg_xml:tbs_wfautog_xml status=60 dumpfile=exp_wfat
g_20100421.dmp parallel=2 directory=dumpdirdd
The problem:
i have WFAT tables with triggers that belong to WFATG , WFPATG and WFAUTOG users !!!
why ???
Best regards
Rui Madaleno

Hi Paul,
thanks for you reply
I have followed your suggestion and removed the shemas=wfat option from the impdp command.
Here are the steps:
1) create the user wfautog
Note that , before the import i've created the tablespaces and the wfautog user:
CREATE USER WFAUTOG
IDENTIFIED BY xxxxxx
DEFAULT TABLESPACE TBS_WFAUTOG_TAB
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for WFAUTOG
GRANT CONNECT TO WFAUTOG;
GRANT RESOURCE TO WFAUTOG;
ALTER USER WFAUTOG DEFAULT ROLE ALL;
-- 1 System Privilege for WFAUTOG
GRANT UNLIMITED TABLESPACE TO WFAUTOG;
2) import data:
f:\impdp system/passwordXXX remap_schema=wfat:wfautog remap_ta
blespace=tbs_wfatg_tab:tbs_wfautog_tab remap_tablespace=tbs_wfatg_idx:tbs_wfauto
g_idx remap_tablespace=tbs_wfatg_xml:tbs_wfautog_xml status=60 dumpfile=exp_wfat
g_20100421.dmp parallel=2 directory=dumpdirdd
After that i detect the following problems :( :(
1) There are no sequences in the wfautog schema
2) There are triggers owned by wfautog "pointing" to wfat tables
Can you help me ?
This is the log file from impdp:
===================
Import: Release 10.1.0.2.0 - Production on Thursday, 22 April, 2010 8:27
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** remap_schema=wfatg:wfautog remap_tablespace=tbs_wfatg_tab:tbs_wfautog_tab remap_tablespace=tbs_wfatg_idx:tbs_wfautog_idx remap_tablespace=tbs_wfatg_xml:tbs_wfautog_xml status=60 dumpfile=exp_wfatg_20100421.dmp parallel=2 directory=dumpdir
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"WFAUTOG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PASSWORD_HISTORY
Processing object type SCHEMA_EXPORT/SE_PRE_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "WFAUTOG"."LOGSTRANSFERENCIAS" 46.60 MB 866193 rows
. . imported "WFAUTOG"."PASTAS" 35.89 MB 1273050 rows
. . imported "WFAUTOG"."PROCESSOS" 100.9 MB 422797 rows
. . imported "WFAUTOG"."DOCUMENTOSPROCESSOS" 24.59 MB 345854 rows
. . imported "WFAUTOG"."TRANSFERENCIA_AS400" 18.09 MB 569333 rows
. . imported "WFAUTOG"."CODIGOS_POSTAIS" 8.258 MB 195516 rows
. . imported "WFAUTOG"."ANOTACOESPROCESSOS" 6.840 MB 71609 rows
. . imported "WFAUTOG"."ALERTASPROCESSOS" 4.533 MB 58447 rows
. . imported "WFAUTOG"."PROCESSO_CLINICO" 1.740 MB 27211 rows
. . imported "WFAUTOG"."COMUNICACAO_PRESTADOR" 1.171 MB 11955 rows
. . imported "WFAUTOG"."TEXTOSAUTPROCESSOS" 1018. KB 6784 rows
. . imported "WFAUTOG"."PS_TXN" 310.5 KB 100 rows
. . imported "WFAUTOG"."TAREFA" 716.2 KB 15227 rows
. . imported "WFAUTOG"."MOTIVOS_COMUNICACAO" 205.7 KB 18455 rows
. . imported "WFAUTOG"."AUTORIZACOESPROCESSOS" 152.8 KB 1904 rows
. . imported "WFAUTOG"."AGENDA_UTILIZADOR" 96.92 KB 2647 rows
. . imported "WFAUTOG"."TRIBUNAL_TRABALHO" 104.2 KB 987 rows
. . imported "WFAUTOG"."AGENDA_DOCS" 65.59 KB 4422 rows
. . imported "WFAUTOG"."DOC_COM_PRESTADOR" 88.28 KB 6479 rows
. . imported "WFAUTOG"."PRESTADOR" 53.29 KB 354 rows
. . imported "WFAUTOG"."TRIBUNAL" 47.07 KB 304 rows
. . imported "WFAUTOG"."ACORDAO" 5.281 KB 3 rows
. . imported "WFAUTOG"."ADVOGADO" 6.453 KB 38 rows
. . imported "WFAUTOG"."AGENDA_ALERTAS" 10.50 KB 387 rows
. . imported "WFAUTOG"."AGENDA_AUTORIZACOES" 5.632 KB 31 rows
. . imported "WFAUTOG"."EVT_AGENDA" 28.15 MB 600474 rows
. . imported "WFAUTOG"."XML_PROC_AS400" 0 KB 0 rows
. . imported "WFAUTOG"."AGENDA_TAREFAS" 6.273 KB 77 rows
. . imported "WFAUTOG"."AREASGESTAO" 6.945 KB 19 rows
. . imported "WFAUTOG"."AREASGESTAOUTILIZADOR" 15.14 KB 919 rows
. . imported "WFAUTOG"."CONCELHOS" 12.00 KB 308 rows
. . imported "WFAUTOG"."CONFIGURACOES" 11.54 KB 117 rows
. . imported "WFAUTOG"."CONTACTOS_ESCRITORIO" 7.484 KB 57 rows
. . imported "WFAUTOG"."CORRESPONDENCIA_MODELOS" 6.789 KB 15 rows
. . imported "WFAUTOG"."DISTRITOS" 5.757 KB 29 rows
. . imported "WFAUTOG"."ESCRITORIOS" 11.67 KB 61 rows
. . imported "WFAUTOG"."ESCRITORIOS_UTILIZADOR" 7.609 KB 139 rows
. . imported "WFAUTOG"."ESTADOS_ALERTA" 5.281 KB 3 rows
. . imported "WFAUTOG"."ESTADOS_AUTORIZACAO" 5.328 KB 5 rows
. . imported "WFAUTOG"."ESTADO_CLINICO" 5.328 KB 8 rows
. . imported "WFAUTOG"."ESTADO_COMUNICACAO" 5.390 KB 8 rows
. . imported "WFAUTOG"."ESTADO_EXAME" 5.289 KB 3 rows
. . imported "WFAUTOG"."ESTADO_JUNTA_MEDICA" 5.289 KB 3 rows
. . imported "WFAUTOG"."ESTADO_PROCESSO" 5.312 KB 5 rows
. . imported "WFAUTOG"."ESTADO_PROC_CLINICO" 5.281 KB 3 rows
. . imported "WFAUTOG"."ESTADO_REEMBOLSO" 5.734 KB 6 rows
. . imported "WFAUTOG"."ESTADO_TAREFA" 5.312 KB 5 rows
. . imported "WFAUTOG"."ESTADO_TC" 5.281 KB 3 rows
. . imported "WFAUTOG"."ESTADO_TENT_CONC" 5.335 KB 4 rows
. . imported "WFAUTOG"."ESTADO_TT" 5.296 KB 4 rows
. . imported "WFAUTOG"."EVT_EVENTO" 5.906 KB 8 rows
. . imported "WFAUTOG"."EVT_GRUPO" 5.257 KB 1 rows
. . imported "WFAUTOG"."FAX_QUEUE" 8.976 KB 43 rows
. . imported "WFAUTOG"."FORMATOSDOCUMENTO" 5.398 KB 10 rows
. . imported "WFAUTOG"."FORMA_CAUCAO" 5.304 KB 3 rows
. . imported "WFAUTOG"."FUNCIONALIDADES" 6.140 KB 9 rows
. . imported "WFAUTOG"."FUNCIONALIDADES_PERFIS" 5.484 KB 24 rows
. . imported "WFAUTOG"."GENERIC_ERRORS" 9.328 KB 33 rows
. . imported "WFAUTOG"."GRUPOS_LOG" 5.476 KB 12 rows
. . imported "WFAUTOG"."HOSPITAL_CLINICA" 20.82 KB 124 rows
. . imported "WFAUTOG"."HOSP_CLIN_REDE_MED" 6.476 KB 124 rows
. . imported "WFAUTOG"."INDISPUTILIZADOR" 9.234 KB 58 rows
. . imported "WFAUTOG"."INSTANCIA" 5.281 KB 3 rows
. . imported "WFAUTOG"."IP_DEFINIDA" 5.265 KB 4 rows
. . imported "WFAUTOG"."IP_PRESUMIVEL" 5.273 KB 4 rows
. . imported "WFAUTOG"."MEDICO" 16.21 KB 236 rows
. . imported "WFAUTOG"."MED_HOSP_CLIN" 5.265 KB 4 rows
. . imported "WFAUTOG"."MOTIVOS_POR_TENT_CONC" 5.257 KB 2 rows
. . imported "WFAUTOG"."MOTIVOS_TIPO_PRESTADOR" 6.929 KB 26 rows
. . imported "WFAUTOG"."MOTIVO_TENT_CONC" 5.414 KB 6 rows
. . imported "WFAUTOG"."NOME_TAREFA" 7.125 KB 27 rows
. . imported "WFAUTOG"."ORIGEM_EXAME" 5.265 KB 2 rows
. . imported "WFAUTOG"."PERFIS" 5.375 KB 8 rows
. . imported "WFAUTOG"."PERFISUTILIZADOR" 11.10 KB 272 rows
. . imported "WFAUTOG"."PERITO_MEDICO" 19.53 KB 307 rows
. . imported "WFAUTOG"."PLAN_TABLE" 18.26 KB 10 rows
. . imported "WFAUTOG"."PROCESSOSABERTOS" 5.617 KB 20 rows
. . imported "WFAUTOG"."RAMOS" 6.085 KB 11 rows
. . imported "WFAUTOG"."REDE_MEDICA" 5.375 KB 6 rows
. . imported "WFAUTOG"."REGIME_ASSISTENCIA" 5.273 KB 2 rows
. . imported "WFAUTOG"."REPRESENTANTE" 9.929 KB 97 rows
. . imported "WFAUTOG"."REPRESENTANTE_TEMP" 10.07 KB 8 rows
. . imported "WFAUTOG"."RESULTADO_SENTENCA" 5.281 KB 2 rows
. . imported "WFAUTOG"."TENTATIVA_CONCILIACAO" 8.218 KB 3 rows
. . imported "WFAUTOG"."TIPOSDOCUMENTO" 7.859 KB 71 rows
. . imported "WFAUTOG"."TIPOS_PASTA" 6.304 KB 6 rows
. . imported "WFAUTOG"."TIPO_CAUCAO" 5.296 KB 3 rows
. . imported "WFAUTOG"."TIPO_EXAME" 5.312 KB 3 rows
. . imported "WFAUTOG"."TIPO_HOSPITALCLINICA" 5.312 KB 3 rows
. . imported "WFAUTOG"."TIPO_IP" 5.343 KB 7 rows
. . imported "WFAUTOG"."TIPO_PRESTADOR" 5.343 KB 5 rows
. . imported "WFAUTOG"."TIPO_TRIBUNAL" 5.289 KB 2 rows
. . imported "WFAUTOG"."TRANSPORTE_ESPECIAL" 5.312 KB 5 rows
. . imported "WFAUTOG"."TRIBUNAL_CIVEL" 25.10 KB 18 rows
. . imported "WFAUTOG"."UTILIZADORES" 22.97 KB 196 rows
. . imported "WFAUTOG"."ACTUALIZACAO_LOG" 0 KB 0 rows
. . imported "WFAUTOG"."ACTUALIZACOESAS400" 0 KB 0 rows
. . imported "WFAUTOG"."AGENCIASFAX" 0 KB 0 rows
. . imported "WFAUTOG"."AREASPERFIL" 0 KB 0 rows
. . imported "WFAUTOG"."EXAMES" 0 KB 0 rows
. . imported "WFAUTOG"."FERIADOS" 0 KB 0 rows
. . imported "WFAUTOG"."JUNTA_MEDICA" 0 KB 0 rows
. . imported "WFAUTOG"."LOGSLOGINS" 0 KB 0 rows
. . imported "WFAUTOG"."LOGSPROCESSOS" 0 KB 0 rows
. . imported "WFAUTOG"."PERFISAREA" 0 KB 0 rows
. . imported "WFAUTOG"."PERMISSOES" 0 KB 0 rows
. . imported "WFAUTOG"."PKGLOG_TAB" 0 KB 0 rows
. . imported "WFAUTOG"."SENTENCA" 0 KB 0 rows
. . imported "WFAUTOG"."TRANSF_DEFINITIVAS_ERRORS" 0 KB 0 rows
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/PACKAGE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/FUNCTION/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PROCEDURE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."DEVOLVE_1_PARTICIP_PROC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."DEVOLVE_NOME_PRESTADOR_PC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."DEVOLVE_ULTIMO_RELATMED_PROC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."SMS_FAX_HANDLER" created with compilation warnings
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."DAR_TOMAR_CONHECIMENTO_HANDLER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."FAX_COMPROVATIVO_HANDLER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."SEND_FAX_CORRESPONDENCIA" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."TROCA_GESTOR" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."WFAT_JOB_ENGINE_HANDLER" created with compilation warnings
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."SINISTRO_WEBSERVICE_HANDLER" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."TRANSFERE_DEFINITIVO_PKG" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."VERIFICA_INDISPONIBILIDADES" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."ACTIVACAO_AGENDA_PKG" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."CLASSIFICACAO_PKG" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."PKG_UTILS" created with compilation warnings
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_INS_ALERTAS_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_INS_ALERTAS_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_UPDT_AUT_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_UPDT_AUT_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INSERT_AGENDA_UTIL_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INSERT_AGENDA_UTIL_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ACOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ACOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ADV" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ADV" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ALRT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ALRT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ANOT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ANOT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_AUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_AUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_CPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_CPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_DOCP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_DOCP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECOM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECOM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EJM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EJM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EPROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EPROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ESTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ESTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EXM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EXM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FCAU" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FCAU" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FUNC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FUNC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_GRPL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_GRPL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_HOSP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_HOSP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INDISP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INDISP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPD" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPD" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_JMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_JMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LGP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LGP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LOGT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LOGT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_NTF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_NTF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_OEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_OEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PCL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PCL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERFS_UTIL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERFS_UTIL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PST" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PST" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PTR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PTR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RAS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RAS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_REP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_REP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RSEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RSEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_SEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_SEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TAR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TAR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TCONC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TCONC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TESP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TESP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPA" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPA" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPE" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPE" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPIP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPIP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRANSF_AS400" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRANSF_AS400" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRIB" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRIB" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TXT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TXT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_UPD_AGENDA_UTILIZADOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_UPD_AGENDA_UTILIZADOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_BEF_INS_ESC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_BEF_INS_ESC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_AFT_INS_AGENDA_UTI" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_AFT_INS_AGENDA_UTI" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_BEF_DEL_AGENDA_UTI" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_BEF_DEL_AGENDA_UTI" created with compilation warnings
Processing object type SCHEMA_EXPORT/TABLE/INDEX/SE_TBL_FBM_INDEX_INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/SE_TBL_FBM_IND_STATS/INDEX_STATISTICS
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 150 error(s) at 08:35
Regards
Rui Madaleno

Question about import database pk, fk

Similar Messages

Maybe you are looking for