Purge the database default...

Is there a way to purge old records in the database by default... SQL CE?

We need to upgrade to a full version of SQL, but until I would serve some data from the previous month, so I can at least see activity yesterday.

Thanks for the help!

-Evan

Hey Evan,

Here's the article for SQL Server:

http://communities.quest.com/docs/doc-14838

Your retention settings (Configuration-> retention settings) will only be applied when you stop and start your server service NMS Quest (ptserverservice.exe).

Apart from this, stop the services you can manually delete all the files in data .sdf file. DO NOT DELETE ptdb.sdf. This file contains all of your devices, policies and other settings.

c:\programdata\quest software\nms\nms server\nms db\

Best regards

Jonas

Tags: Dell Tech

Similar Questions

Purge the database postgres VCSA 5.5 data (tables vpx_event & vpx_event_arg)?

Someone at - it instructions for the removal of the entries in the vpx_event & vpx_event_arg for the postgres database tables in VCSA 5.5? Due to a bad person designed the monitoring scripts, we have 18 million rows in the vpx_event_arg table and looks like it is the root cause of our recent problems with the VCSA.
I see several KB articles on how to purge the data from MS SQL Server, but not instructions for Postgres. So the same manully kickoff roll-up scripts. I've updated the retention policy of database from 180 to 90 days, but there is still 18 M records in the table. Cannot find how to manually start the rolling script for postgres.
Any help would be appreciated.
Thank you
Michael

Could not find a clean way to purge the data from the table, so we finished truncating the entire table. I poured both the vpx_event and the tables of vpx_event_arg for archival purposes and then did:

/opt/VMware/vpostgres/1.0/bin/psql d VCDB vc

Enter the password

then:

TRUNCATE TABLE vpx_event WATERFALL;

It takes only a minute and of course we were back in business and the performance was back to normal.

How to purge the windows live photo gallery database of missing files

I recently moved most of my photos on a removable drive from SD. Of course, photo gallery can not find them and I can't point the Pb on a removable drive. Please tell us how do I purge the database of photo gallery of found files.

Might be interesting to try to rename the Photo Live
Gallery database file.

The "Pictures.pd4, .pd5 or .pd6' (according to
on the version of your photo gallery), database includes
inches and metadata and is located at the following
location.

C:\Users\[username]\AppData\Local\Microsoft\
Windows Photo Gallery\Pictures.pd4, .pd5.
or .pd6

The file ends with a advanced
Research of pd4 pd5 and pd6.

Reach... Start / Search / Advanced search.

Check the box... "include not indexed, hidden,
and the file system"enter pd4, pd5 pd6 in the
Name field

Rename the .pd5 .pd4 or pd6 file should
clean your library.

Try a click right/rename it... Pictures.OLD
If you are not satisfied with the results... you can
Delete the new file and rename the OLD file
Back to Pictures.pd4, .pd5 or .pd6.

Photo Gallery will return to what it was the first
time that you opened it. The gallery will have to re-
complete and you may lose some tags.

How do you set up when TMS purge the information from its database?

Hi all

I would purge the Pb on my TMS server and cannot find information on how to do it.

My server is encountering the limit of 4 GB for the DB SQL 2005 I have running. I want to prevent the server from suffocation, so I pulled back the number of days THAT TMS stores for newspapers but he cannot find a way to initiate a purge so the DB can make room for new conferences.

I know what's happening every night at midnight, but I prefer to be able to open the purge now.

Is anyway to do this? Is there a way to change the default time of calendar purge?

Thanks for the help,

Shawn

You cannot manually start the jobs of the TMS product interfaces. They will work based on the calendar automatically in the background.

To see when they will work, Goto administrative tools-> active and look for the work listed as "purge the data expired in the tables.

BTW, if you upgrade to SQL Express 2008 2012, the database limit is much higher (10 GB). In addition, support for 2005 will be removed from newer versions of TMS little.

Purge the rman backup
Hello, since the alert.log file find this error:

Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
ORA-19809: limit exceeded for file recovery
ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
ARC3: 19809 creation error archive log file ' DATA01'+.
Sea 25 09:51:58 Jan 2012
Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
************************************************************************
You have choice to free up space in the recovery area:
+ 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
then consider changing POLICY of DELETE ARCHIVELOG RMAN.
+ 2. Back up files on a tertiary device such as a tape using RMAN.
SAFEGUARDING RECOVERY AREA command.
+ 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
reflect the new space.
+ 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
the system control has been used to remove the files, and then use the RMAN DUPLICATION and
Commands DELETE has EXPIRED.
************************************************************************
Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
ORA-19809: limit exceeded for file recovery
ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
ARC0: error creating 19809 archive log file ' DATA01'+.

So I'm trying to purge the rman backup, but I have an error message:

rman target = oratest@oraprdlnx1:~$ /+.
Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: TEST (DBID = 2044700519)

+ RMAN > show all; +.

using the control file of the target instead of recovery catalog database
RMAN settings for database with db_unique_name TEST are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default

+ RMAN > allocate channel for maintenance of type; disc +.

allocated channel: ORA_MAINT_DISK_1
channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK

+ RMAN > crosscheck backup; +.

"" element of verified backup: turned out to be "AVAILABLE"
backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
Cut objects 1

RMAN > delete obsolete; ** +

RMAN retention policy apply to the order
RMAN retention policy is set to 1 redundancy
Remove the following obsolete backups and copies:
Making key time filename/handle type
-------------------- ------ ------------------ --------------------
Backup Set 25 July 4, 11
Backup total 25 4 July 11 1omgk64v_1_1
Backup Set 26 July 4, 11
Backup total 26 July 4, 11 1pmgk650_1_1
Backup Set 24 July 4, 11
Total backup, 24 4 July 11 1qmgk650_1_1
Backup Set 21 July 4, 11
Backup total 21 4 July 11 1rmgk650_1_1
Backup Set 28 July 4, 11
28 1vmgk69v_1_1 July 4, 11 total backup
Save game 29 July 4, 11
Backup total 29 July 4, 11 20mgk6a0_1_1
Backup Set 30 July 4, 11
Backup total 30 4 July 11 21mgk6a0_1_1
Save game 31 July 4, 11
Backup total 31 July 4, 11 22mgk6a0_1_1
Backup Set 34 4 July 11
Backup total 34 4 July 11 c-2044700519-20110704-07
Backup Set 35 July 4, 11
Total backup, 35 26mgk8ib_1_1 4 July 11
Backup Set 36 4 July 11
Backup total 36 4 July 11 c-2044700519-20110704-08
Backup Set 41 4 July 11
Backup total 41 4 July 11 28mgk94i_1_1
Backup Set 42 4 July 11
Backup total 42 4 July 11 29mgk94j_1_1
Backup Set 37 July 4, 11
Backup total 37 4 July 11 2amgk94j_1_1
Backup Set 40 July 4, 11
Backup total 40 July 4, 11 2bmgk94j_1_1
Backup Set 38 July 4, 11
Backup total 38 4 July 11 2cmgk95c_1_1
Backup Set 39 July 4, 11
Backup total 39 4 July 11 2dmgk95k_1_1
Backup Set 43 July 4, 11
Backup total 43 July 4, 11 c-2044700519-20110704-09
Backup Set 46 4 July 11
Backup total 46 4 July 11 2fmgk99f_1_1
Backup Set 47 July 4, 11
Backup total 47 4 July 11 2gmgk99g_1_1
Backup Set 44 4 July 11
Backup total 44 4 July 11 2hmgk99g_1_1
Backup Set 48 4 July 11
Backup total 48 4 July 11 2imgk99g_1_1
Backup Set 45 4 July 11
Backup total 45 4 July 11 2jmgk9a9_1_1
Backup Set 50 4 July 11
Backup total 50 4 July 11 2kmgk9aq_1_1
Backup Set 49 July 4, 11
Backup total 49 4 July 11 2lmgk9aq_1_1
Backup Set 51 4 July 11
51 4 July total backup has 11 c-2044700519-20110704-0
Backup Set 56 4 July 11
Total backup 56 2rmgk9qb_1_1 July 4, 11
Backup Set 55 July 4, 11
Backup total 55 4 July 11 2smgk9qb_1_1
Backup Set 58 4 July 11
Backup total 58 4 July 11 b c-2044700519-20110704-0
Backup Set 60 4 July 11
Total backup 60 2umgk9tb_1_1 July 4, 11
Backup Set 61 4 July 11
Backup total 61 4 July 11 2vmgk9tc_1_1
Backs up the entire 62 4 July 11
Backup total 62 4 July 11 30mgk9tc_1_1
Backup Set 66 4 July 11
Backup total 66 4 July 11 34mgk9ua_1_1
Backs up the entire 65 4 July 11
Backup total 65 4 July 11 35mgk9ua_1_1
Backup Set 67 4 July 11
Total backup, July 4, 11 c-2044700519-20110704-0 67C
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
RMAN-06091: any string allocated for maintenance (of a suitable type)

How can I purge the db dest file recovery?

Thank you!!!
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
RMAN-06091: any string allocated for maintenance (of a suitable type)

There is a metalink note that talks about this error.

Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

HTH

Kind regards
Nagendra Chillale

Published by: NC on January 25, 2012 17:00

DDF mount data to the database

Dear:

I need to design an application to read the data of the DDF file and mount them in database.

Could you please let me know how I can design an application to read these DDF files.

I offered to do the next step:

1 binary reading the orginal DDF file

2 convert to ASCII code

3. Finally, following the DASYLab format to enter data and transfer to the database file.

Thank you

There are two ways to do this:

First of all, just read the data using the DATA module to READ and write again with a DATA WRITE module configured to ASCII. Please see the ASCII options to ensure that the data separator, date/time format and the number of decimal places to your needs.

Make sure that you configure the DATA module to READ to read NOT in real time. The default is to replay in real-time.

Second, read the data using the DATA READING module and use the module output of ODBC and an Action to write directly to the database module. This implies relatively slow data and cannot be done at high speed.

Convert the database to 10 v to v11

Hello

I'm unable to convert and merge a v10.1 v11 user database. I made a backup of Usrcomp_S.usr to another folder in Windows then used the merger of Multisim and Ultiboard and conversion tools. Here are the steps I followed:

1 tools > Database > convert database...

2. Select Source in the dialog context database names.

3. navigate to the database using the Windows dialog box. Select my copy of database using "All Files." Curiously he is not using the default filter. Select OK and then the following error:

The path of the database: "database\UsrComp_S.usr" was not found or not set.
You want to select the path where the database of component?

4. Select Yes then select my now visible database of the dialog Windows.

5. press start to convert my database to aid auto rename. Briefly, something happens that seems to be the conversion and the window convert watch Done

6. close the convert and open tools > database > merge a database...

7. Select a name of the component database

8. Repeat step 3 above. The allegedly converted database is still not visible but this time there is no option to "All Files." In the file name drop-down box I choose the path previously used for the database copy. Select open and receive the following error message:

The path of the database: "database\UsrComp_S.usr" was not found or not set.
You want to select the path where the database of component?

9. Select Yes then select my now visible database of the dialog Windows.

10. press on open and receive the following error message:

Error: Could not open the database [user data].
The file format/version does not, and cannot be merged.
If the database is from a previous version, use convert the database.

Help, please. This should be a simple process of a button to import parts of the user of a previous version.

Richard

Hi Richard,

I think you are trying to convert the incorrect database. From the name you specified (Usrcomp_S.usr), it's just a CDS model uses to create a user database, it is not your user database.

On Windows XP, the user database is located in C:\Documents and Settings\\Application Data\National Instruments\Circuit Design Suite\11.0\database\

On Windows Vista/7, the user database is located in C:\Users\\AppData\Roaming\National Instruments\11.0\database\

EMERGENCY: Opening of a MS Access 2003 database in Ms 2003 and Vista simultaneously irremediably corrupts the database, erasing all forms.

EMERGENCY: Opening of a MS Access 2003 database in Ms 2003 and Vista simultaneously irremediably corrupts the database, erasing all forms. It is a progressive company upgrade to Ms Windows and Office 2003 to Ms Vista and Office 2007. Some users now have the Vista Machines and still others 2003 machines. They all share the object database, which resides on a SQL Server. When the database is opened in 2003 and Vista users at the same time, the forms are destroyed and the database is permanently damaged.

Means of access:

http://answers.Microsoft.com/en-us/Office/default.aspx

Office at the above link forums

http://social.answers.Microsoft.com/forums/en-us/addbuz

Access support at the link above.

They will help you with your questions of access when repost you in the Office Forums above.

See you soon.

Mick Murphy - Microsoft partner

Failed to load existing records from the database on SD card during initialization of the application

When the Simulator is launched upward, not able to load existing records from the database in the Inbox, so no records appear in the Inbox even though they exist in the database. It seems to be a problem with the SD card in the Simulator - the file system for the SD card is not correctly initialized when the application starts first to the top. During initialization of the application tries to access the SD card by using the following code.

Boolean

sdCardPresent = false;

Enumeration e = FileSystemRegistry.listRoots ();

If

(e! = null) { }

While (e.hasMoreElements ()) {}

root = (String) e.nextElement ();

If

(root.equalsIgnoreCase("SDCard/")) {

sdCardPresent =

true;

}

}

}

sdCardPresent is always set to false and was not able to access existing records from the database. Once the application is initialized and try to create the database, the database is created successfully on the SD card. The code is the same as above when creating the database and was able to do sdCardPresent = true.

Is there anyway to register or add the SD card during initialization of the application or any property as System.setProperty overide the path of the default directory value?

I use BlackBerry 9550 Simulator. I checked the "file system using PC for files from the SD card" and I use "C:\bb\SDCard" for the file system of thr.

Also tested on the BlackBerry and found the same thing, if the device is hard reset, then it not reading the SD card as well.

Mark the thread as solved then.

Accessing an application WebWorks built the database via a Java application

Hi all

My Java application needs to access a database that was created by a WebWorks built application. I see WebWorks encryption applications their databases using the code keys automatically signing. When I first tried to read the database, he said that it was encrypted as IOException: headers are encrypted. Since then, I installed the same key code in my Eclipse IDE to signature and have signed the java application with the same keys used by the WebWorks app. I always seem to get an IOException error, but this time it does not specify the exact error.

Quite simply, I need to use the same database created in the WebWorks app in my Java application. Is it possible if I use the same code key for both signature requests? Or WebWorks uses a completely different algorithm to encrypt data in the database from Eclipse and so cannot use the same database?

Thank you for all your help.

Rob

Yes, the DB is encrypted by default by using the identity of the application (code signing key and I believe in association with the name of the application)

Thus, the type of DB of SQLite that is created from a WebWorks app is different from one created from a Java application, which can be a conflict at stake here.

If you believe that it is a Google Gears database!

https://github.com/BlackBerry/WebWorks/BLOB/master/framework/src/js/html5_init.js#L586

Well Yes, to subsidize bequests to devices BBOS 5.0, which had no WebKit as web rendering engine, Gears is the 'wedge' up here.

For the above reasons, I do not think that its going to be possible for you to achieve what you're trying with SQLite DB. To share data between applications on BBOS, you would need to use a different channel (encrypt the data and save it in the file system, or use your own remote web service + DB)

cannot select a mapped drive on select the database window

I use virtual XP mode in Windows 7. Under XP, I am able to map a drive G: that comes from Win 7 mapped drive (Microsoft Terminal Services). Great, in Explorer, you can see the mapped drive. I need to set up an ODBC connection to a database on this disc. No problem, I thought. When I need to select a drive in the select the database window, I do not see this drive only A:, C:, D:, the default value for readers, G: is not displayed.

Is this a bug or is this normal? I did something wrong?

Any help would be appreciated.

Thank you

I finally solved it.

I've got a hold of our network knowledgeble person and have been able to connect a network drive. It was enough to format another/prefix in the login window. Then I set up an ODBC for the Access database.

It seems that virtual XP does not meet tsclient, so had to use windows normal mapping.

Another problem solved!

Link to the database of Oracle 11 g 11.2.0.3.0 to SQLServer 2012 - 11.0.5058.0 (X 64)

Hello.
I read a lot of discussion and documentation on this subject, but the things I'm trying to work.
I want to connect from Oracle to SQL Server. I did the following steps:
(Taking into account, that I want to connect to a database SQL SERVER called GS2PIASQL03\INSTANCE3)
Create the odbc connection in the oracle called running GS2PIASQL03 Server
Name: GS2PIASQL03
Description: GS2PIASQL03
Server: GS2PIASQL03\INSTANCE3
With authentication sql server using a login ID and passwotrd entered by the user
Connect to sql server to obtain default settings for the configuration option extra
User: rema_read
Password: xxxxxxx
Master default database
Use ANSI quoted identifiers
Use nulls, padding and ANSI warnings
Perform the conversion of character data
Finishing and test the source data before TESTS COMPLETED successfully.
Content of LISTENER.ora
listener.ora # Network Configuration file: S:\app\oracle\product\11.2.0\dbhome_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = S:\app\oracle\product\11.2.0\dbhome_1)
(= Extproc PROGRAM)
(ENVS = "EXTPROC_DLLS=ONLY:S:\app\oracle\product\11.2.0\dbhome_1\bin\oraclr11.dll")
)
(SID_DESC =
(SID_NAME = CRM)
(ORACLE_HOME = S:\app\oracle\product\11.2.0\tg_1)
(PROGRAM = S:\app\oracle\product\11.2.0\tg_1\bin\dg4odbc.exe)
)
(SID_DESC =
(SID_NAME = CRMSVC)
(ORACLE_HOME = S:\app\oracle\product\11.2.0\tg_1)
(PROGRAM = dg4odbc)
)
(SID_DESC =
(GLOBAL_DBNAME = REMA)
(ORACLE_HOME=S:\app\oracle\product\11.2.0\dbhome_1)
(SID_NAME = REMA)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = SLPIAM29)(PORT = 1521))
(ADDRESS = (PROTOCOL = CIP)(KEY = EXTPROC1521))
)
)
ADR_BASE_LISTENER = S:\app\oracle
Content of the TNSNAMES file. ORA
tnsnames.ora # Network Configuration file: s:\app\oracle\product\11.2.0\dbhome_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.

GS2PIASQL03 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = tcp)
(HOST = 172.16.61.18)
(PORT = 1521)
)
(CONNECT_DATA = (SID = GS2PIASQL03))
(HS = OK)
)
Content of initGS2PIASQL03.ora
HS_FDS_CONNECT_INFO = GS2PIASQL03
#HS_FDS_SHAREABLE_NAME = C:\Windows\System32\odbc32.dll
HS_FDS_TRACE_LEVEL = Debug
Stop and start receiving and then create a database link running the following command in Toad:
CREATE THE DATABASE LINK TEST_SQLS PUBLIC
To CONNECT to "read_rema".
IDENTIFIED BY 'password '.
WITH THE HELP OF 'GS2PIASQL03 '.
/
When I test the link of database (with the option of Toad) or run a query such as:
Select * of sys.sysobjects@TEST_SQLS;

I get the same error
*********************************************************************
Link: "TEST_SQLS".
Error: ORA-28545: error diagnosed by Net8 when connecting to an agent
Cannot retrieve the text of the message NETWORK/NCR 65535
ORA-02063: preceding 2 lines of TEST_SQLS
*********************************************************************
Please I really need your help I really really need this to work and I'm completely lost know.
I look forward to hearing from you soon.
Vinny.

Hey Vinny,

No, the host tnsnames.ora must not refer to the place where the SQL * Server database is active. The tnsnames.ora entries is intended to guide the user who calls the database link by using this entry to a listener running on the computer and the port in the entry. The listener then directs the user to everything that is referenced by the SID in the listener. If it is an Oracle database, then you are linked to the database. If this is an entry of gateway referenced by having the (HS = OK) then you are linked to the gateway which then liaises with what non-Oracle database is accessible through the gateway of the option. You cannot directly connect to the non-Oracle database by using the IP address of machine non-Oracle in tnsnames.ora. You need to go through the door entry referenced by the listener to establish the connection.

For the listener, you can set the path to the ORACLE_HOME of the gateway or RDBMS. However, the best option is to give the listener a different name from the default, so for the gateway, you might have-

SID_LIST_LISTENER_GTW =

(SID_LIST =

(SID_DESC =

(SID_NAME = GS2PIASQL03)

(ORACLE_HOME=S:\app\oracle\product\11.2.0\tg_1)

(PROGRAM = dg4odbc)

)

)

LISTENER_GTW =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = SLPIAM29)(PORT = 1525))

(ADDRESS = (PROTOCOL = CIP)(KEY = EXTPROC1525))

)

)

You can then use-

stop LISTENER_GTW

Start LISTENER_GTW

Kind regards

Mike

Lovs cascading in a table, see the stored default value

Hi all.
I use 5 APEX.
I need to create a Select list based on another inside a tabular presentation, I have followed this thread: How to make the selection list cascading in the form of? and when I add a new line it works OK, the problem is once I have save changes, if I have access to the tabular presentation page again every row shows 'Selection' - and the value that is stored in the database is not shown by default, the list is built according to the LOV parent for existing lines, but will return to the Mode "selection", that vary according to the initial behavior in the form of tables.
Please help me to show the stored value for the lines already stored.
Thanks in advance, best regards.

Hi all.

The problem is in the definition of the child selection list, I changed the "display additional values" field to YES and now it works perfectly.

Concerning

Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

Here's my question after tons of research and test without have the right solutions.
Target:
(1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".
(2) I created physical standby database "stbydb" on the server "node2".
(3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.
(4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)
(5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)
(6) I do RMAN backup (database and archivelog) on the site of relief only.
(7) I want to use this backup for full restore of the database on the primary database.
He is a DR test to simulate the scenario that has lost every primary & Eve total servers.
Here is how to save, on the database pending:
(1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files
(2) RMAN > backup database;
(3) RMAN > backup archivelog all;
I got elements of backup and copied to primary db Server something like:
/Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)
/Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)
/Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)
So here's how to restore, on the main site:
I clean all the files (data files, controlfiles oder all gone).
(1) restore spfile from pfile
RMAN > startup nomount
RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
(2) modify pfile to convert to db primary content. pFile shows below
*.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '
* .audit_trail = "db".
* full = '12.1.0.2.0'
*.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'
* .db_block_size = 8192
* .db_domain = "
*.db_file_name_convert='/testdb/','/testdb /'
* .db_name = "testdb".
* .db_recovery_file_dest ='/ orafra'
* .db_recovery_file_dest_size = 10737418240
* .db_unique_name = "testdb".
*.diagnostic_dest='/opt/Oracle/DB '
* .fal_server = "stbydb".
* .log_archive_config = 'dg_config = (testdb, stbydb)'
* .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"
* .log_archive_dest_state_2 = 'ENABLE '.
*.log_file_name_convert='/testdb/','/testdb /'
* .memory_target = 1800 m
* .open_cursors = 300
* runoff = 300
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
(3) restart db with updated file pfile
SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'
SQLPLUS > the judgment
SQLPLUS > startup nomount
(4) restore controlfile
RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
RMAN > change the editing of the database
(5) all elements of backup catalog
RMAN > catalog starts by ' / home/oracle/backupset / '.
(6) restore and recover the database
RMAN > restore database;
RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)
(7) open resetlogs
RMAN > alter database open resetlogs;
Everything seems perfect, except one of the file log roll forward pending is not generated
SQL > select * from v$ standby_log;
ERROR:
ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3
no selected line
I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.
So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.
And I got the same missing log file.
The problem is:
(1) complete alert.log filled with this error, not the concern here
(2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."
(3) I can't delete and re-create this log file
Then I tried several and found:
The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.
For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 19 ACTIVE 133632
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
So until I take the backup, I tried on the primary database:
SQL > alter system set log_archive_dest_state_2 = delay;
This was the Group of standby_log side Eve #4 was released:
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 0 0 UNASSIGNED
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
Then, the backup has been restored correctly without missing standby logfile.
However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.
Finally, my real questions come:
(1) what I do may not do on parameter change?
(2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?
I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...
And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.
I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.
Your idea is very much appreciated.
Thank you!

Hello

1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

2nd--> when we opened the ORL database should be deleted and created

3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

THREAD # SEQUENCE # GROUP # STATUS

---------- ---------- ---------- ----------

1 233 4 ACTIVE

1 238 5 ACTIVE

DR sys@cdb01 SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_ CON_ID

---------- ------- ------- ------------------------------ --- ----------

3 /u03/cdb01/cdb01/redo03.log no. 0 online

/U03/cdb01/cdb01/redo02.log no. 0 2 online

1 /u03/cdb01/cdb01/redo01.log no. 0 online

4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

/U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

DR sys@cdb01 SQL > alter database force claire logfile 4;

change the database group claire logfile 4

*

ERROR on line 1:

ORA-01156: recovery or current flashback may need access to files

DR sys@cdb01 SQL > alter database recover managed standby database cancel;

Database altered.

DR sys@cdb01 SQL > change the database group claire logfile 4;

Database altered.

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

DR sys@cdb01 SQL >

If you do, you can recreate the controlfile without waiting for redo log entry...

If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

Thank you

BEA-000362 < server failed. At least a migratable target is configured with automatic migration. Before the automatic migration of any type can be used, the MigrationBasis must be defined in the ClusterMBean. If the database is selected, then DataSourc

My Weblogic 12 c StartWeblogic.cmd failed after that I configured the migration of the cluster to the database with the name of the table as none. I can't even to the Server Admin page.
Before that, I remove the. log.lck, process.id, process.lck files in the nodemanager directory
Help, please! Thank you!
Joe
****************************************************************************
# < October 1, 2015 4:18:20 PM CDT > < Info > < security > < NAP1D692 > <>< Home > <><><>< 1443734300986 > < BEA-090905 > < disable provider JCE CryptoJ self-int├⌐grit├⌐ for better startup performance. To allow this control, enter - Dweblogic.security.allowCryptoJDefaultJCEVerification = true. >
# < October 1, 2015 4:18:21 PM CDT > < Info > < security > < NAP1D692 > <>< Home > <><><>< 1443734301049 > < BEA-090906 > < change the default Random Number Generator in RSA CryptoJ of ECDRBG128 to FIPS186PRNG. To disable this change, specify - Dweblogic.security.allowCryptoJDefaultPRNG = true. >
# < October 1, 2015 4:18:21 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > <>< Home > <><><>< 1443734301064 > < BEA-000395 > < the following extensions added at the end of the classpath directory content:
C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\lib\log4j-1.2.15.jar; C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\lib\wllog4j.jar. >
# < October 1, 2015 4:18:21 PM CDT > < Info > < WebLogicServer > < NAP1D692 > <>< Thread-4 > <><><>< 1443734301361 > < BEA-000377 > < since Java hotspot 64-bit Server VM WebLogic Server Version 24.60 - b09 of Oracle Corporation. >
# < October 1, 2015 4:18:21 PM CDT > < Info > < management > < NAP1D692 > <>< Thread-5 > <><><>< 1443734301610 > < BEA-141107 > < Version: WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 >
# < October 1, 2015 4:18:22 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > <>< Thread-6 > <><><>< 1443734302702 > < BEA-000365 > < Server State has changed at the START. >
# < October 1, 2015 4:18:22 PM CDT > < Info > < WorkManager > < NAP1D692 > <>< Thread-6 > <><><>< 1443734302702 > < BEA-002900 > < init > self-adjustable thread pool.
# < October 1, 2015 4:18:22 PM CDT > < Info > < WorkManager > < NAP1D692 > <>< ExecuteThread [ASSET]: '0' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734302733 > < BEA-002942 > < CMM level memory becomes 0. Sleep thread pool to 256. >
# < October 1, 2015 4:18:22 PM CDT > < Info > < WebLogicServer > < NAP1D692 > <>< Thread-6 > <><><>< 1443734302733 > < BEA-000214 > < WebLogic Server "AdminServer" version:
WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 Copyright (c) 1995,2014, Oracle and/or its affiliates. All rights reserved. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol 't3' is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "t3s" is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < the 'http' Protocol is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < the "https" Protocol is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "iiop" is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol 'iiops' is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < "ldap" Protocol is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "ldaps" is now set up. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "cluster" is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol 'clusters' is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < the "SNMP" is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "admin" is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002624 > < administration Protocol is "t3s" and is now configured. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < RJVM > < NAP1D692 > <>< Thread-5 > <><><>< 1443734303264 > < BEA-000570 > < Network Configuration for channel "AdminServer.
Listening address: 7001
Address public n/a
True active http
Tunneling Enabled false
Outgoing Enabled false
Admin traffic enabled true fake license to ResolveDNSName >
# < October 1, 2015 4:18:23 PM CDT > < Debug > < RJVM > < NAP1D692 > <>< Thread-5 > <><><>< 1443734303264 > < BEA-000571 > < retail network for channel "AdminServer.
Weight of the channel 50
Accept the rear 300
Timeout 5000ms
Message Max Size 10000000
Timeout message 60 years
Timeout of 65
Tunneling Timeout 40 s
Tunneling Ping 45 s >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-5 > <><><>< 1443734303279 > < BEA-002609 > < channel Service initialized. >
# < October 1, 2015 4:18:23 PM CDT > < opinion > < Log Management > < NAP1D692 > <>< ExecuteThread [pending]: '1' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734303357 > < BEA-170019 > < C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\logs\AdminServer.log server log file is opened. All events in the log server-side will be written to this file. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Log Management > < NAP1D692 > <>< ExecuteThread [pending]: '1' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734303404 > < BEA-170023 > < logging of the server is initialized with the Java application logging API. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < IIOP > < NAP1D692 > <>< [STANDBY] ExecuteThread: '2' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734303404 > < BEA-002014 > < subsystem enabled IIOP. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Log Management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303404 > < BEA-170025 > < initialized Logging area. Events in the field log will be written to C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\logs/joe12c_domain.log. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Diagnostics > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303451 > < BEA-320001 > < ServerDebug The service initialized successfully. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303513 > < BEA-280008 > < open the persistent store of file 'WLS_DIAGNOSTICS' for recovery: directory = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\data\store\diagnostics requestedWritePolicy = "Disabled" fileLockingEnabled = true driver = "wlfileio3." >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303529 > < BEA-280103 > < storage of persistent files "WLS_DIAGNOSTICS" puts in cache in weblogic.store.io.file.direct.FileMapping [granularity = 65536 io mapped =]. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303529 > < BEA-141278 > < Java configuration entropy is: property system "java.security.egd = null; File JRE java.security "securerandom.source = file:/dev/urandom" property Blocking of the Config = false; Version of the JDK = 1.7.0_60; Operating system = Windows 7. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303545 > < BEA-141280 > < configuration detected NON-BLOCKING of entropy of java. This setting you will give the best performance on machines with limited sources of entropy, but is less secure than a blocking entropy configuration. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303545 > < BEA-141187 > < Java System properties are defined as follows:
awt. Toolkit = sun.awt.windows.WToolkit
leader. Encoding = Cp1252
leader. Encoding.pkg = sun.io
leader. Separator =.
Java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
Java.awt.PrinterJob = sun.awt.windows.WPrinterJob
Java.class.Path = C:\JDK17~1.0_6\lib\tools.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic_sp.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\net. SF.antcontrib_1.1.0.0_1-0b3\lib\ant-contrib.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\modules\features\oracle.WLS.common.nodemanager_2.0.0.0.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\com. Oracle.Cie.config - WLS - online_8.1.0.0.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derbyclient.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derby.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\xqrl.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.jar; C:\Progra~2\IBM\RATION~1\CLEARQ~1\cqjni.jar
Java.class.version = 51.0
Java.endorsed.dirs = C:\JDK17~1.0_6\jre\lib\endorsed; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed
Java.ext.dirs = C:\JDK17~1.0_6\jre\lib\ext; C:\Windows\Sun\Java\lib\ext
Java.Home = C:\JDK17~1.0_6\jre
Java.IO.TMPDIR =
Java.Library.Path = C:\JDK17~1.0_6\bin; C:\Windows\Sun\Java\bin; C:\Windows\System32; C:\Windows; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\native\win\x64; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\bin; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\org. Apache.ant_1.9.2\bin; C:\JDK17~1.0_6\jre\bin; C:\JDK17~1.0_6\bin; C:\Progra~2\IBM\RATION~1\common; C:\Progra~3\Oracle\Java\javapath; C:\oracle\product\102~1.0\client_1\BIN; C:\Progra~2\BUSINE~1\Common\3.5\bin\NOTES\; C:\Windows\System32; C:\Windows; C:\Windows\System32\wbem; C:\Windows\System32\WINDOW~1\v1.0\; C:\Progra~2\HEAT\;\\nap-lvip-047\scmref\bin; C:\JDK17~1.0_5;\\nap-lvip-047\maven\M3R1SW~N.9\bin; C:\Progra~2\CODECO~1;\\nap-lvip-047\scmref\bin; C:\Windows\System32; C:\Progra~2\IBM\gsk8\lib; C:\Progra~2\IBM\gsk8\bin; C:\Progra~2\IBM\RATION~1\CLEARC~1\Bin; C:\Progra~2\IBM\RATION~1\CLEARC~1\REMOTE~1\cteapis; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\native\win\x64\oci920_8;.
Java.naming.Factory.initial = weblogic.jndi.WLInitialContextFactory
Java.naming.Factory.URL.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
Java.Runtime.Name = Java (TM) SE Runtime Environment
Java.Runtime.version = 1.7.0_60 - b19
Java.Security.Policy = C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.policy
Java.Specification.Name = Java Platform API Specification
Java.Specification.Vendor = Oracle Corporation
Java.Specification.version = 1.7
Java.Vendor = Oracle Corporation
Java.vendor.URL = http://Java.Oracle.com/
Java.vendor.URL.bug = http://bugreport.Sun.com/bugreport/
Java.version = 1.7.0_60
Java.VM.info = mixed mode
Java.VM.Name = VM Server Java hotspot 64-Bit
Java.VM.Specification.Name = specification of Machine Java virtual
Java.VM.Specification.Vendor = Oracle Corporation
Java.VM.Specification.version = 1.7
Java.VM.Vendor = Oracle Corporation
Java.VM.version = 24, 60 - b09
javax. Management.Builder.initial = weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
OS. Arch = amd64
OS. Name = Windows 7
OS.version = 6.1
Path.Separator =;
Sun.Arch.Data.Model = 64
Sun.Boot.class.Path = C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed\javax-xml-bind.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed\javax-XML-WS.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed\jsr250-API.jar; C:\JDK17~1.0_6\jre\lib\resources.jar; C:\JDK17~1.0_6\jre\lib\rt.jar; C:\JDK17~1.0_6\jre\lib\sunrsasign.jar; C:\JDK17~1.0_6\jre\lib\jsse.jar; C:\JDK17~1.0_6\jre\lib\jce.jar; C:\JDK17~1.0_6\jre\lib\charsets.jar; C:\JDK17~1.0_6\jre\lib\jfr.jar; C:\JDK17~1.0_6\jre\classes
Sun.Boot.Library.Path = C:\JDK17~1.0_6\jre\bin
Sun.CPU.endian = little
Sun.CPU.isalist = amd64
Sun.Desktop = windows
Sun.IO.Unicode.Encoding = UnicodeLittle
Sun.java.Command = weblogic. Server
Sun.java.Launcher = SUN_STANDARD
Sun.JNU.Encoding = Cp1252
Sun.Management.Compiler = HotSpot 64 bits compilers Tiered
Sun.OS.patch.Level = Service Pack 1
User.country = en
User.dir = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain
User.Home =
User.language = en
User.Name =
User.TimeZone =
VDE. Home = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\data\ldap
WebLogic. Name = AdminServer
WebLogic.Home = C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server
WLS. Home = C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server
. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303545 > < BEA-280009 > < storing files persistent "WLS_DIAGNOSTICS" (75765a60-c009-403f-a7ed-c6a75a86e1c8) has been opened: blockSize = 512 actualWritePolicy = "Disabled(single-handle-non-direct)" explicitIOEnforced = false files = 25. " >
# < October 1, 2015 4:18:23 PM CDT > < Info > < XML > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303592 > < BEA-130036 > < XMLRegistry initialization >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Socket > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303662 > < BEA-000436 > < allocate 4 player son. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < Socket > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303662 > < BEA-000446 > < active native to IO. >
# < October 1, 2015 4:18:23 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303849 > < BEA-000000 > < OpenJPA starting 1.1.1 - SNAPSHOT >
# < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304005 > < BEA-000000 > < StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_PyMqKeZifftJZ2SHXoWLnh4Ldn4 = >
# < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304021 > < BEA-090516 > < authenticator provider has already given LDAP. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304114 > < BEA-090516 > < provider authorized person a pre-existing LDAP data. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304301 > < BEA-090516 > < CredentialMapper a pre-existing LDAP provider data. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304317 > < BEA-090516 > < RoleMapper a pre-existing LDAP provider data. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304379 > < BEA-090093 > < no pre - WLS 8.1 Keystore provider is configured for server security realm myrealm AdminServer. >
# < October 1, 2015 4:18:24 PM CDT > < opinion > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304379 > < BEA-090082 > < security initialization using security realm myrealm. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < connector > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304457 > < BEA-190000 > < J2EE Connector Service initialization. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < connector > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304457 > < BEA-190001 > < Service connector J2EE initialized successfully. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304473 > < BEA-280008 > < opening persistent store file '_WLS_AdminServer' for recovery: directory = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\data\store\default requestedWritePolicy = fileLockingEnabled 'Direct entry' = true driver = "wlfileio3." >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304504 > < BEA-149512 > < JMX connector server started service: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.runtime. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304535 > < BEA-040305 > < JMS service is initialized and standby mode. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040090 > < 8 deployed by default connection factories. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory2' with 'weblogic.jms.XAConnectionFactory2' JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'MessageDrivenBeanConnectionFactory' with 'weblogic.jms.MessageDrivenBeanConnectionFactory' JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultConnectionFactory' with 'weblogic.jms.ConnectionFactory' JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'TopicConnectionFactory' with his "javax.jms.TopicConnectionFactory" JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory' with 'weblogic.jms.XAConnectionFactory' JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory0' with 'weblogic.jms.XAConnectionFactory0' JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < default connection factory is started 'Factory' with his "javax.jms.QueueConnectionFactory" JNDI name >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory1' with 'weblogic.jms.XAConnectionFactory1' JNDI name is started >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040306 > < JMS service is now active. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304629 > < BEA-149512 > < JMX connector server started service: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.domainruntime. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < ExecuteThread [ASSETS]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304676 > < BEA-280009 > < file persistent store "_WLS_AdminServer" (c54c7ab9-2eab-4095-ba3c-5abb38f06231) has been opened: blockSize = 512 actualWritePolicy = "Direct-Write(read-buffered)" explicitIOEnforced = false documents = 21. " >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304691 > < BEA-149512 > < JMX connector server started service: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.edit. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304769 > < BEA-001135 > < init > the JDBC service.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304785 > < BEA-001137 > < full initialization >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304785 > < BEA-001138 > < Recovery > JDBC service.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304785 > < BEA-001140 > < complete resume >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < messaging.interception > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304816 > < BEA-400000 > < initialization message interception service. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < Server > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304863 > < BEA-002622 > < Protocol "[https, t3, snmp, cluster-broadcast-secure, ldaps, cluster-broadcast, ldap, http, iiop, admin, t3s '. "[, iiops]" is now set up. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304863 > < BEA-101128 > < HTTP initialization services. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304894 > < BEA-101135 > < AdminServer is the default Web server. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304894 > < BEA-101052 > < [HttpServer (defaultWebserver) name: AdminServer] Initialized >
# < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304894 > < BEA-101129 > < init > the container of the Web application.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304972 > < BEA-149513 > < JMX Connector Server stopped serving: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.edit. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001144 > < Force suspending the JDBC service. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001146 > < Force suspend completed JDBC service >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001147 > < JDBC service stop. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001149 > < stopping the JDBC service performed. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-149513 > < JMX Connector Server stopped serving: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.domainruntime. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < MessagingBridge > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-200001 > < messaging bridge has shut down successfully. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-040308 > < service JMS suspends >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-040107 > < 8 cancelled by default connection factories. >
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-040015 > < stop JMS is done >.
# < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-149513 > < JMX Connector Server stopped serving: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.runtime. >
# < October 1, 2015 4:18:24 PM CDT > < critical > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734304988 > < BEA-000362 > <Server has failed. Reason: at least a migratable target is configured with automatic migration. Before the automatic migration of any type can be used, the MigrationBasis must be defined in the ClusterMBean. If database is chosen, must be set so DataSourceForAutomaticMigration. >
# < October 1, 2015 4:18:25 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000365 > < Server state changed to FAILED. >
# < October 1, 2015 4:18:25 PM CDT > < error > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000383 > < is not an essential service. The server shuts itself down. >
# < October 1, 2015 4:18:25 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000365 > < Server state has changed to FORCE_SHUTTING_DOWN. >
# < October 1, 2015 4:18:25 PM CDT > < Info > < WebLogicServer > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000236 > < stop run > discussions.
# < October 1, 2015 4:18:25 PM CDT > < Info > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000238 > < judgment made. >

It may sound crazy that I am answering my own post. As he complains about MigrationBasis. I tried to go to the config.xml file and changed

Cluster-0

unicast

database

TO

Cluster-0

unicast

consensus

And at least I was able to restart Server Admin and go to the Server Admin page. The Cluster-> Configuration-> Migration is always on view from database as the basis for Migration.

Joe

Purge the database default...

Similar Questions

Maybe you are looking for