2012年10月12日 星期五

您所輸入的網路介面卡IP位置已經被指派給另一個介面卡XXX的問題


這問題源自於發生在將A Server端用 VMware vCenter Converter 將OS做成 vmdk 的映像檔然後掛載在VM上。因為轉換後網卡不同了,因此原本在A台主機上的網卡上設定10.10.10.22 (example) 到了VM 上的VM-A主機上要再設定相同的IP時會出現下列的錯誤訊息  

英譯: This network adapter is already assigned to another adapter XXXXXXX on this compuetr"
中譯: 您輸入的網路介面卡IP位置已經被指派給另一個介面卡 XXXXXXX


以前有時候運氣很好,從控制台把隱藏網卡叫出來刪掉就好了....但這次居然找不到? 搞了很久發現有更簡單的方式
解決方式:
1. 開始 ->執行 ->輸入regedit (打開登錄檔編輯器)
2.尋找下列機碼位置
HKEY_LOCAL_MACHINE\SYSTEMCurrent\ControlSet\Services\Tcpip\Parameters\Interfaces

在Interfaces 機碼底下放著都是設定網卡的資訊,你可以點選每一個來看,
但是哪一個才是我想要的呢?

因為看不出來所以才每一個都點開來看,就應該會發現有一個居然已經有10.10.10.22 ,這表示這個資料夾就是已經消失在VM系統中的舊網卡,因此把此把對應的做邊資料夾機碼刪掉後,你在去修改一次IP就會發現很神奇的可以儲存了。













2012年7月17日 星期二

VMware-用 vmkfstools Clone一個新的VM OS

因為沒有安裝 Vcenter的關係所以在要不斷的複製出新的VM OS其實是很麻煩的(沒辦法滑鼠點點就完成 XD )

解決方法:

1. 每次都建立一個新的設定檔然後用光碟片安裝OS  <<(當然不建議嚕)


2.先做成一個Sample OS , 然後用 vmkfstools 來做clone


指令如下:
vmkfstools -i /vmfs/(volumes name)/(Storage name)/(folder name)/(file name).vmdk -d thin
/vmfs/(volumes name)/(Storage name)/(folder name)/(file name).vmdk







Vmkfstools 參數如下:


OPTIONS FOR FILE SYSTEMS: 



vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath

OPTIONS FOR VIRTUAL DISKS:

vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:<device>|rdmp:<device>|
                                2gbsparse]
               -N --avoidnativeclone
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -I --snapshotdisk srcDisk
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath

OPTIONS FOR DEVICES:

           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|readresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...


2012年5月18日 星期五

Cisco Aironet1262N-快速連接GUI

最近剛入手 Cisco Aironet 1262N 的 無線Access Point ,很開心的把它拿出來,這體積還真的有點大
老實說我也是第一次碰到這種脫離SOHO的無線AP

但....要怎樣連接到GUI??

連接GUI 介面方法:

1.使用DHCP 進行IP配法: 如果有架設DHCP Server 網路一插上去就 BVI1 Interface就會自動派發到IP,所以查一下DHCP Server 對照一下Cisco Aironet背面的MAC Address就可以知道是哪個IP了。

2.使用Consol介面指定BVI1 介面IP /Mask 及Gateway


EWSW01#
EWSW01#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
EWSW01(config)#int BVI1
EWSW01(config-if)#ip add
EWSW01(config-if)#ip address 10.10.11.203 255.255.255.224
EWSW01(config-if)#no sh
EWSW01(config-if)#exit

EWSW01(config)#ip default-gateway 10.10.10.254



這樣一來就可以連到Cisco Aironet 的GUI 介面,是不是很簡單呢.....

2012年5月15日 星期二

Cisco Aironet 設定 SSH


Configure Secure Shell (SSH) on an Access Point

CLI Configuration
In this section, you are presented with the information to configure the features described in this document
with the use of CLI.Step−by−Step Instructions
In order to enable SSH−based access on the AP, you first must configure the AP as an SSH server. Follow
these steps in order to configure an SSH server on the AP from CLI:
Configure a host name and domain name for the AP.
AP#configure terminal

!−−− Enter global configuration mode on the AP.

AP<config>#hostname Test
!−−− This example uses "Test" as the AP host name.

Test<config>#ip domain name abc.com
!−−− This command configures the AP with the domain name "abc.com".
1.
Generate a Rivest, Shamir, and Adelman (RSA) key for your AP.
Generation of an RSA key enables SSH on the AP. Issue this command in global configuration mode:

Test<config>#crypto key generate rsa rsa_key_size
!−−− This generates an RSA key and enables the SSH server.
Note: The recommended minimum RSA key size is 1024.
2.
Configure user authentication on the AP.
On the AP, you can configure user authentication to use either the local list or an external
authentication, authorization, and accounting (AAA) server. This example uses a locally generated list
in order to authenticate the users:

Test<config>#aaa new−model


!−−− Enable AAA authentication.
Test<config>#aaa authentication login default local none
!−−− Use the local database in order to authenticate users.

Test<config>#username Test password Test123
!−−− Configure a user with the name "Test".

Test<config>#username ABC password xyz123
!−−− Configure a second user with the name "ABC".

This configuration configures the AP to perform user−based authentication with the use of a local
database that is configured on the AP. The example configures two users in the local database, "Test"
and "ABC".
3.
Configure the SSH parameters.
Test<config>#ip ssh {[timeout seconds] | [authentication−retries integer]}
!−−− Configure the SSH control variables on the AP.
4. Note: You can specify the timeout in seconds, but do not exceed 120 seconds. The default is 120.
This setting applies to the SSH negotiation phase. You can also specify the number of authentication
retries, but do not exceed five authentication retries. The default is three.
GUI Configuration
You can also use the GUI in order to enable SSH−based access on the AP.
Step−by−Step Instructions
Complete these steps:
Log in to the AP through the browser.
The Summary Status window displays.
1.
Click Services in the menu on the left.
The Services Summary window displays.
2. Click Telnet/SSH in order to enable and configure the Telnet/SSH parameters.
The Services: Telnet/SSH window displays. Scroll down to the Secure Shell Configuration area. Click
Enable beside Secure Shell, and enter the SSH parameters as this example shows:
This example uses these parameters: EXAMPLE
♦ System Name: Test
♦ Domain Name: abc.com
♦ RSA Key Size: 1024
♦ Authentication Timeout: 120
♦ Authentication Retries: 3
3. 4. Click Apply in order to save the changes.
Verify
Use this section to confirm that your configuration works properly.
The Output Interpreter Tool ( registered customers only) (OIT) supports certain show commands. Use the OIT to
view an analysis of show command output.
show ip ssh Verifies if SSH is enabled on the AP and enables you to check the version of SSH that
runs on the AP. This output provides an example:

show ssh Enables you to view the status of your SSH server connections. This output provides an
example:

Now, initiate a connection through a PC that runs third−party SSH software and then make an attempt to log
in to the AP. This verification uses the AP IP address, 10.0.0.2. Because you have configured the user name
Test, use this name in order to access the AP through SSH:Troubleshoot
Use this section to troubleshoot your configuration.
If your SSH configuration commands are rejected as illegal commands, you have not successfully generated
an RSA key pair for your AP. Refer to the Troubleshooting Tips section of the document Configuring Secure
Shell for a list of possible reasons for this problem.Disable SSH
In order to disable SSH on an AP, you must delete the RSA pair that is generated on the AP. In order to delete
the RSA pair, issue the crypto key zeroize rsa command in global configuration mode. When you delete the
RSA key pair, you automatically disable the SSH server. This output provides an example:
Related Information
• Configuring Secure Shell
• Configuring the Access Point for the First Time
• Secure Shell (SSH) Support Page
• Wireless Support Page
• Technical Support & Documentation − Cisco Systems
Contacts & Feedback | Help | Site Map
© 2009 − 2010 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Nov 05, 2008 Document ID: 68789

2012年2月26日 星期日

Oracle DB Clone fail

我真的很氣....最近Clone DB 的時候都不能夠一次就搞定,弄得我的實在有點不太爽
來吧...再來看看這次有什麼問題


$ cd $ORACLE_HOME/appsutil/clone/bin
$ perl adcfgclone.pl dbTier

跑一段時間後大概在70%後因錯誤而停止.....


Backing up /OOXX/testdb/9.2.0/appsutil/OOOOerpt1.xml to
/OOXX/testdb/9.2.0/appsutil/ OOOOerpt1 .xml2.bak

Creating the new Database Context file from :
   /OOXX/testdb/9.2.0/appsutil/template/adxdbctx.tmp

The new database context file has been created :
  /OOXX/testdb/9.2.0/appsutil/OOOOerpt1..xml

Log file located at /OOXX/testdb/9.2.0/appsutil/clone/bin/CloneContext_02241130.log

Running Rapid Clone with command:
        perl /OOXX/testdb/9.2.0/appsutil/clone/bin/adclone.pl java=/OOXX/testdb/9.2.0/appsutil/clone/bin/../jre/jre mode=apply stage=/OOXX/testdb/9.2.0/appsutil/clone/bin/.. component=dbTier method=CUSTOM dbctxtg=/OOXX/testdb/9.2.0/appsutil/OOOOerpt1..xml  showProgress contextValidated=true

Beginning database tier Apply - Fri Feb 24 11:31:51 2012
Log file located at /OOXX/testdb/9.2.0/appsutil/log/OOOOerpt1./ApplyDBTier_02241131.log
RC-50004: Fatal: Error occurred in ApplyDatabase:
Control file creation failed
ERROR while running Apply...
 ERROR: Failed to execute /OOXX/testdb/9.2.0/appsutil/clone/bin/adclone.pl 
 Please check logfile.
$

  <<<就在這理可以大概知道主要的問題,然後透過log去看一下到底是在那一段裡有問題





一看到Control file creation failed  error ....我就又暈了...之前遇過好幾次這種問題
其實一開始也不知道為什麼資料夾的權限都會有問題,會使系統在寫入資料時因為權限不足
推測了一下有可能我都是用root的權限在複製Datafile 所以即一開始沒有確實的先把資料與資料夾chown 成等要操作的帳號擁有者權限,就很容易miss而產生這問題

而無法寫入導致錯誤,這個解法大致如下:

方法一 : chown  資料夾 讓資料夾在擁有作者的權限
ex:  chown - oraprod:dba 資料夾名稱

方法二.chmod: 修改寫入的權限
ex:  chmod - 775 資料夾名稱




然後重新執行DB clone ,  如果仍是失敗.....那麼這Datafiles已經無效,請刪除重新再複製一次新的Datafiles過來唄!!!!!

解決Oracle ERP Target node/queue unavailable 問題

最近也算很賽.....只要Clone DB 沒有一次就搞定的,好不容易DB終於Clone成功,ERP AP 也可以運作.....但AP Team 的人反應, Concurrent Manage沒反應

Orz........

看了一下AP 發現 Actual 都是0 ...Status都出現 Target node/queue unavailable
以往Actual 都是0的時候,前人都說Shutdown 在 Restare應該就好了,但..........
 Target node/queue unavailable ???? 啥米鬼阿




網路上查了一下有關於 Target node/queue unavailable的資料,每個都很像但不知道哪個可以用,所以全部都找了一下解答,後來發現最相近的就是Note 555081.1 因為我真的是Clone完之後就不行了XD  


*** Target node/queue unavailable ***
Note 2104027.6:  Conflict Resolution Manager Does Not Start After Install, Upgrade or Patch Application 
Note 736024.1 :  Unable to Bring Up Concurrent Manager after Running Autoconfig. 
Note 735148.1 : How to Troubleshoot Concurrent Manager Start Up Issue Related to Service Manager
Note 218893.1 : How to Create The Service Manager 'FNDSM' on Oracle Applications
Note 260887.1 : Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES
Note 423170.1 : Concurrent Manager Fails to Start Because of a 'Could not start Service Manager FNDSM__' Error
Note 430812.1 : After Linux Version Upgrade FNDSM Does Not Spawn
Note 555081.1 : After Doing a Clone All the Concurrent Managers Do Not Start

在我看完關於555081的敘述時...我還蠻開心的因為看起來好像就是解決方法,

The issued was found to have been caused by the FND_NODES table having incorrect node entries (old node from the Source Instance) and that no Service Manager was found for the existing node.

但OOXX 的是我不會啊下面寫得密密麻麻的我哪知道怎樣做啊.....步驟1-4我覺得還OK,步驟五就好笑了因為沒跟我說檔名是甚麼我還是用SUN系統的,這下就傷腦筋了好不容易東翻翻西翻翻翻到檔案在哪 

我的步驟是
先用apps登入sqlplus中先看一下現在是怎樣的狀態
語法:  select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%'; 

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

$ sqlplus

SQL*Plus: Release 9.2.0.7.0 - Production on Sun Feb 26 09:28:27 2012

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Enter user-name: apps
Enter password: OOXX

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production

SQL> select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

CONCURRENT_QUEUE_NAME
------------------------------ 
FNDSM_OOXXERPT1  <<只有一個,但這是有問題的,一開始我也不知道
------------------------------------------------------------------------------------------------

接下然按照所述的進行
1. Stop all middle tier services including the concurrent managers. 
2. Stop the database. 
3. Start the database (請務必將Listener也啟動,不然等你執行DB 的autoconfig以後你就會在Log下看到這樣的訊息
ERROR:
ORA-12541: TNS:no listener
ERRORCODE = 1 ERRORCODE_END




4. Connect SQLPLUS as APPS user and run the following : 

SQL>EXEC FND_CONC_CLONE.SETUP_CLEAN; 
SQL>COMMIT; 
SQL>EXIT; 


執行完這段以後再列出一次你會發現CONCURRENT_QUEUE_NAME空空如也

SQL> select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

CONCURRENT_QUEUE_NAME
------------------------------ 



5. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables. 

AutoConfig  from DB path:    $ORACLE_HOME//9.2.0/appsutil/scripts/your_host_name/adautocfg.sh
(DB status was start)

AutoConfig  from AP path:    $ORACLE_HOME/admin/scripts/your_host_name/adautocfg.sh
(AP staus was shutdown)

先做DB tier 完成後再做 AP Ttier ,兩個都完成後再Select 一次

CONCURRENT_QUEUE_NAME
------------------------------
FNDSM_APEXTWERPT1  << 原來的那個
FNDSM_AUTHENTICATION  <<新出現的,如果有人知道這認證是幹嘛的或是會不見得原因也請跟我說一下呢!


(PS: 如果到了步驟六還不能搞定,請繼續參閱後續步驟)


接著把AP開啟,並登入ERP > Concurrent > Manager > Administartor 再看一次 Target node/queue unavailable消失了且Actual 也都有反應.





後續.......每次Clone結束後我都好開心...因為整個過程就是很痛苦...難道都沒有更簡單的方法按個按鈕或是打個指令就可以一路到底嗎? 還是因為我公司的DB 跟ERP 實在太舊了所以只能用一些辦自動的方式搞定

當下好想唱一下小春哥的 神啊~救救我吧





以下資訊轉載從
http://hi.baidu.com/big_tree_ivan/blog/item/8f7df20f2a1014e037d12223.html
=====================================================================

NOTE:555081.1

==============

Applies to:

Oracle Application Object Library - Version: 11.5.9 to 12.0  
This problem can occur on any platform.

Symptoms

In Oracle Application Release 11i and 12 , After doing a clone when attempting to start the concurrent manager using the below :

. adcmctl.sh stop apps/apps under $COMMON_TOP/admin/scripts/<Hostname>/

the below error can be found in ICM logfile :
===========
Could not initialize the Service Manager FNDSM_<HOSTNAME>_<SID>. Verify that <HOSTNAME> has been registered for concurrent processing.
===========

Cause

The issued was found to have been caused by the FND_NODES table having incorrect node entries (old node from the Source Instance) and that no Service Manager was found for the existing node.

Solution

1. Stop all middle tier services including the concurrent managers.

2. Stop the database.

3. Start the database.

4. Connect SQLPLUS as APPS user and run the following :

EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

=========================
Article- ID : 260887.1
Title: Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES
=========================
( Note : In the case of a clone instance, it is strongly recommended to clean the non - existing nodes )

5. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables.

6. Connect to SQLPLUS as APPS user and run the following statement :

select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%'; 

If the above SQL does not returning any value then please do the following:

Go to $FND_TOP/patch/115/sql

Connect SQLPLUS as APPS user and run the following script :

SQL> @afdcm037.sql;

=========================
Article-ID : 218893.1
Title: How to Create The Service Manager 'FNDSM' on Oracle Applications
=========================
(Note : The same "afdcm037.sql" is used for Release 12 also ).

This script will create libraries for FNDSM and create managers for preexisting nodes.

Check again that FNDSM entries now exist:

select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

7. Go to cd $FND_TOP/bin
$ adrelink.sh force=y "fnd FNDLIBR"
$ adrelink.sh force=y "fnd FNDSM"
$ adrelink.sh force=y "fnd FNDFS"
$ adrelink.sh force=y "fnd FNDCRM"

8. Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
=========================
Article- ID : 134007.1
Title: CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
=========================
9. Start the middle tier services including your concurrent manager.
10. Retest the issue .
==============================****************************************************************************
The cause of this problem is the change of FNDSM trigger in ATG RUP 5.

====================================================
The new FNDSM trigger code is:

CREATE OR REPLACE TRIGGER fndsm
AFTER INSERT ON FND_NODES FOR EACH ROW
BEGIN
if ( :new.NODE_NAME <> 'AUTHENTICATION' ) then
if ( (:new.SUPPORT_CP='Y') or (:new.SUPPORT_FORMS='Y') or (:new.SUPPORT_WEB='Y') ) then
fnd_cp_fndsm.register_fndsm_fcq(:new.NODE_NAME);
end if;
if (:new.SUPPORT_CP = 'Y') then
fnd_cp_fndsm.register_fndim_fcq(:new.NODE_NAME);
end if;
end if;
END;
====================================================

When we run autoconfig on db tier, new row inserted into FND_NODES but FNDSM and FNDIM are not created since db tier not supported CP/FORMS/WEB.
When we run autoconfig on apps tier, this columns are updated to 'Y' but FNDSM trigger is not run because it is fired for insert and not for update.

The Solution is :
1) Recreate the FNDSM trigger same as before but add "AFTER INSERT OR UPDATE ON FND_NODES".
2) Run: exec FND_CONC_CLONE.setup_clean; (with apps)
3) Run autoconfig on db tier and apps tier (in this order)
4) Startup apps tier.

There is no patch at this time to fix this probem, but when ATG RUP 6 will be available it will contain a fix to FNDSM trigger.
Full details in Metalink note 434613.1.
==============================**********************************************************

References

Note 134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
Note 218893.1 - How to Create The Service Manager 'FNDSM' on Oracle Applications
Note 260887.1 - Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES




2012年2月23日 星期四

Oracle DB Restore error

其實我只是半調子的DBA,沒有接受過正規的訓練就硬上,真的搞的我好痛苦
因為Oracle ERP 要還原資料庫到測試區,所以開始按照SOP進行操作,對於這個還原動作
其實我做過很多次了,每次也都很順利阿!
不過這兩天在還原的時候一直有問題 ,磁帶機跑個幾分鐘就結束了, 畫面還給我顯示完成

bash-2.03$ rman target / catalog rman/rman@rcat

====================================================================
Recovery Manager: Release 9.2.0.7.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
connected to target database: PROD (not mounted)
connected to recovery catalog database

RMAN> list backup of archivelog from time='sysdate-1';
List of Backup Sets
===================
  List of Archived Logs in backup set 3841856
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    267247  6969521319 23-FEB-12 6969522190 23-FEB-12
  1    267248  6969522190 23-FEB-12 6969529596 23-FEB-12
  1    267249  6969529596 23-FEB-12 6969541532 23-FEB-12
  1    267250  6969541532 23-FEB-12 6969562012 23-FEB-12
  1    267251  6969562012 23-FEB-12 6969583421 23-FEB-12
  1    267252  6969583421 23-FEB-12 6969590201 23-FEB-12
  1    267253  6969590201 23-FEB-12 6969605419 23-FEB-12
  1    267254  6969605419 23-FEB-12 6969626002 23-FEB-12
  1    267255  6969626002 23-FEB-12 6969642047 23-FEB-12
  1    267256  6969642047 23-FEB-12 6969680909 23-FEB-12
  1    267257  6969680909 23-FEB-12 6969710928 23-FEB-12

  1    267258  6969710928 23-FEB-12 6969710946 23-FEB-12
  1    267259  6969710946 23-FEB-12 6969710956 23-FEB-12

RMAN> run
{
allocate channel t1 type 'sbt_tape' parms="ENV=(NB_ORA_CLIENT=OOOprod)";
allocate channel d1 type disk;
restore archivelog from logseq 267258 until logseq 267259;
release channel d1;
release channel t1;
}
2> 3> 4> 5> 6> 7> 8>
allocated channel: t1
channel t1: sid=13 devtype=SBT_TAPE
channel t1: VERITAS NetBackup for Oracle - Release 5.0GA (2005030612)

allocated channel: d1
channel d1: sid=14 devtype=DISK

Starting restore at 23-FEB-12

channel t1: starting archive log restore to default destination
channel t1: restoring archive log
archive log thread=1 sequence=267258
channel t1: restoring archive log
archive log thread=1 sequence=267259
channel t1: restored backup piece 1
piece handle=al_90123_1_775995936 tag=TAG20120223T101834 params=NULL
channel t1: restore complete
Finished restore at 23-FEB-12

released channel: d1

released channel: t1

RMAN> exit




bash-2.03$ vi /AP/OOOprod/clone_prod.sh
"/AP/OOOprod/clone_prod.sh" 20 lines, 475 characters
#!/bin/sh

TARGET_CONNECT_STR=/
CATALOG_CONNECT_STR=rman/rman@rcat

rman target / catalog $CATALOG_CONNECT_STR << EOF
run
{
allocate channel t1 type 'sbt_tape' parms="ENV=(NB_ORA_CLIENT=OOOprod)";
allocate channel d1 type disk;
restore controlfile ;
alter database mount;
set until logseq 267259 thread 1;
restore database;
recover database;
alter database open resetlogs;
release channel d1;
release channel t1;
}
EOF
~
====================================================================



試了好幾次都不行,本來想直接找維護廠商救援,後來很不信邪再是一次,這次用tail -f nohup.out 去看一下輸出的內容發現failed to create file "/PROD_DB/proddata/cntrl01.dbf" ,


====================================================================


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/23/2012 11:36:19
ORA-19504: failed to create file "/PROD_DB/proddata/cntrl01.dbf"
ORA-27040: skgfrcre: create error, unable to create file
SVR4 Error: 13: Permission denied

RMAN>

Recovery Manager complete.
====================================================================



想一下有這種可能的話應該就是資料夾權限有問題, 因此又從新再做了一次 chown -fR oraprod:dba proddata
然後再試一次!


靠.....好了!  當下好想哭喔    搞很久耶


====================================================================
Starting restore at 23-FEB-12
channel t1: starting datafile backupset restore
channel t1: specifying datafile(s) to restore from backup set
restoring datafile 00013 to /PROD_DB/proddata/fax01.dbf
restoring datafile 00022 to /PROD_DB/proddata/cctx01.dbf
restoring datafile 00027 to /PROD_DB/proddata/icxd01.dbf
restoring datafile 00033 to /PROD_DB/proddata/bisd01.dbf
restoring datafile 00034 to /PROD_DB/proddata/bisx01.dbf
restoring datafile 00082 to /PROD_DB/proddata/opix01.dbf
restoring datafile 00104 to /PROD_DB/proddata/bimx01.dbf
restoring datafile 00130 to /PROD_DB/proddata/xdpx01.dbf
restoring datafile 00159 to /PROD_DB/proddata/ontd01.dbf
restoring datafile 00167 to /PROD_DB/proddata/wshd01.dbf
restoring datafile 00184 to /PROD_DB/proddata/iemx01.dbf
restoring datafile 00258 to /PROD_DB/proddata/psbx01.dbf
restoring datafile 00287 to /PROD_DB/proddata/fvd01.dbf
restoring datafile 00302 to /PROD_DB/proddata/enix01.dbf
restoring datafile 00414 to /PROD_DB/proddata/xdod01.dbf

2012年2月17日 星期五

VMware Vsphere5-(Client 安裝)

Vsphere Client 是用來管理Vsphere Server的重要軟體,沒了它就沒搞頭了,安裝過程極為簡單
幾乎是[NEXT]一路到底


檔案下載路徑:
http://downloads.vmware.com/d/info/datacenter_cloud_infrastructure/vmware_vsphere/5_0


1.選擇安裝語系,不過可選的種類不多,有支援簡體中文(但沒繁體),所以還是選擇English吧




3.請點選[NEXT]


4.請點選[NEXT] 


5.請點選I agree to the terms in the license agreement 然後按 [NEXT] 


6.輸入名稱和組織 (兩個都要輸入才可以按NEXT)


7.安裝預設路徑,請點選[NEXT]


8.請點選[Install]


9.請點選[Finish]


如何? 安裝真的很簡單吧 XD

VMware Vsphere5-(Server 初始設定)

接續

在安裝完Vsphere5 Server 後必須要先做一下基本設定,這樣你的Vsphere Client 才有辦法好好的連到Server上



1.一開機就會有Warning 的訊息,是關於DHCP lookup failed ,這是因位並不想再設定好前就接上網路的關係. 不想在還沒完備的情況下就接上網路 (雖然接了也不會怎樣 > <" )



2.按一下ENTER後會跳出要你輸入帳號密碼 (預設帳號 root / 密碼: 就你在安裝時設定的那組


3.這是系統的基本參數設定,身為管理者沒事不要給別人進來玩唷...要是一個不注意給你Restore Default 或是改一下管理密碼...這下就有得瞧了XD
如果有想要改一下密碼的話請點選 [Configure password] 進行修改


4.[Configure Management Network] 是基本參數設定中最重要且必設定的步驟,這邊完成的話系統基本上都能運作


4-1: [Configure Management Network]  > [Network Adapters]
設定預設的連線裝置(本Server有配置四張網路卡所以有四個vmnic) ,請挑一個



4-2: [Configure Management Network]  > [VLAN]
如果你有在Switch Port 上設置好VLAN的話在這請不要填,不然你的網路會不通喔


4-3: [Configure Management Network]  > [IP Configuration]
設定一個連線用的固定IP、遮罩跟閘道



4-4: [Configure Management Network]  > [IPv6 Configuration]
如果你有用IPv6的才需要設定,本範例用IPv4



4-5: [Configure Management Network]  > DNS Configuration]
設定你的DNS 位置,通常公司內都繪設定DNS Server 指到那邊就對了



4-6: [Configure Management Network]  > [Custom DNS suffixes]
設定你的DNS尾碼...通常是指Domain name


5.[Configure Keyboard] 如果想要改Keyboard的種類請自行更改


6.[Troubieshooting Mode Options] 除錯的時候好用的選項


7.[View System Logs] 右邊的1-6想看哪個按一下對硬的數字鍵就會切到該Logs下,想離開的時候請按下[Q]即可...不瞞你說一開始我沒有看到Press  Q to return to this screen這句話...想說要怎樣離開阿!  = =" 後來想說Linux 不是要離開畫面都Q 嗎? 還真不小心讓我離開了 XD


7.[View Support Information ] 右邊會顯示一些相關訊息公你參考可按 [Page up/down]檢視頁面


8.[Reset System Configuration ] 按了就恭喜你在重來一下吧XD


VMware Vsphere5-(Server 安裝)

 Vsphere5 Server 安裝其實真的簡單到爆!!!  看完這篇你也已經是個安裝達人了  \@@ /



1.Vsphere 5 Server 安裝前,首先要先至VMWARE 官網下載ISO安裝檔
依據你要安裝的版本進行下載 (本範例下載的是 Entersprise version)
http://downloads.vmware.com/d/info/datacenter_cloud_infrastructure/vmware_vsphere/5_0


2.下載完畢後請將ISO burn to CD 並放入要安裝的主機光碟機


3.點選 EXSI-5.0.0-20111104001-standard installer


4.要等一下它會開始載入一些資料


5.請按下 [Enter]


6.License Agreement 宣告,請按下[F11] 鍵


7.可用裝置掃描中...請稍等一下


 8.確認安裝位置請按下 [Enter]


9.怕你選錯請Confirm DISK後按下 [Enter]


10.設定Keyboard ,我想絕大部分應該都是US Default ,如果有不同的請自行更改,完成選擇後請按下 [Enter]

11.輸入管理密碼 (預設帳號就是root)


12.系統掃描中......請稍等一下


13.確認是否要安裝,請按下 [Enter]


14.安裝中....請稍等一下


15.恭喜你,安裝好了請按下 [Enter] 系統會重開機



EX1: 如果設定中有出現此訊息....恭喜你,你忘記在BISO裡開啟VT了,建議放棄本次安裝先把VT開起來.




2012年2月15日 星期三

DELL Power Connect 5524 Switch


這兩天為了能夠趕快把可恨的iSCSI SAN架構弄好...不斷的再趕進度,但人嘛~只有兩隻手
實在有點忙不過來,在對於Switch這東西老實說我沒用過DELL 的Switch , 沒想到我的初夜就獻
給了5524...阿不要亂想呢! 是初次不知道該對它做完整的設定害我無法好好入睡的那一夜 XD

這兩天稍微在console裡面游走了一下,其實,操作過程跟Cisco IOS 80%指令都幾乎還蠻像的
這讓我鬆了一口氣....不過當然裡面有一些指令還是有點差異的

如果不想用模擬器或沒預算買不起Cisco Switch的但又想要有點實際的感覺我想這Switch也可以是一種替代品呢!!!! 

就我這兩天稍為摸了一下554跟心得分享:

1.一發現操作方法跟Cisco很像的時候一度有爽度破表的感覺,因為我沒買技術服務所以一切都得自己來, 昨天我在跟Cisco 4500 Switch做port-channel的時候,其中一台5524 不知道再發甚麼神經怎樣都接不起來,我一度還質疑我一定指另亂打...最後居然是5524 的channel-group設的跟4500 一樣就好了!! 在去設另一台....卻不用設定一樣的channel-group一次就搞定! 真的看到鬼
不知道是不是沒擺乖乖還是FW的問題,看來明天上班的時候要先來去更新一下FW

2.看起來像是L2 的switch 卻有L3的本質因為我有看到  ip route 的功能...但是不是這樣可能要再測測才知道.




PowerConnect 5524 規格

操作手冊下載
http://supportapj.dell.com/support/edocs/network/pc5524/



連接埠屬性

  • 24 個 10/100/1000BASE-T 自動感應 Gigabit 乙太網路交換連接埠
    4 個支援光纖媒體的 SFP 組合插槽 (備註:使用 SFP 插槽來取代內建的 10/100/1000BaseT 連接埠)
    支援速度、雙工模式及流量控制的自動協商功能
    自動 MDI/MDIX
    連接埠鏡射
    廣播流量控制

效能

  • 效能 

    交換器光纖頻寬容量為 48.0 Gbps
    轉送率為 35.6 Mpps
    最多至 8,000 個 MAC 位址

可用性

  • 擴充樹 (IEEE 802.1D)、多重擴充樹 (MSTP) 和快速擴充樹 (IEEE 802.1w),支援快速連結
    PowerConnect RPS-600 的外接備援電源支援 (另售)
    纜線診斷 (透過虛擬纜線測試工具進行)

VLAN

  • 每個 IEEE 802.1Q 均具有標記和連接埠型 VLAN 支援;通訊協定型 VLAN
    最多可支援 4000 個 VLAN 
    支援 GVRP 的動態 VLAN
    通訊協定型 VLAN

服務品質

  • 第 2 層信任模式 (IEEE 802.1p 標記)
    第 3 層信任模式 (DSCP)
    每個連接埠有 8 個優先佇列
    可調整的加權循環配置資源 (WRR) 及嚴格佇列排程

多點傳送

  • 動態多重播送支援 – 最多支援 256 個多重播送群組的 IGMP 窺視或靜態多重播送

安全性

  • 最多 128 個 ACL 和 1,000 個 ACE
    交換器存取密碼保護
    使用者可定義設定來啟用或停用 Web、SSH、Telnet、SSL 管理存取
    連接埠型 MAC 位址警示及鎖定
    用來透過 Telnet、HTTP、HTTPS/SSL、SSH 及 SNMP 進行管理存取的 IP 位址篩選
    用於交換器管理存取的 RADIUS 及 TACACS+ 遠端驗證
    用於交換器管理流量的 SSLv3 及 SSHv2 加密
    DHCP 窺視
    透過管理存取設定檔進行管理存取篩選
    IEEE 802.1x 型技術驗證

其他交換功能

  • iSCSI 最佳化與監控
    對外速率調整與對內速率限制
    連結聚合,每個交換器最多可支援 8 個聚合連結,每個聚合連結最多有 8 個成員連接埠 (IEEE 802.3ad)
    LACP 支援 (IEEE 802.3ad)
    支援最高 10K 位元組的巨大封包

管理

  • 可透過 Telnet 或本機序列連接埠存取的業界標準 CLI
    支援 SNMPv1 和 SNMP v2c
    支援 4 個 RMON 群組 (記錄、統計、警告和事件)
    TFTP 韌體與組態檔案傳輸
    主機板內建雙韌體影像
    支援多重組態檔案上傳/下載
    錯誤監視及效能最佳化的統計資料,包括連接埠摘要表
    支援 BootP/DHCP IP 位址管理
    SNTP 支援
    Layer 3 Traceroute
    Telnet 用戶端
    Syslog 遠端記錄功能

機箱

  • 440 x 255 x 44 公釐 (寬 x 深 x 高)
    17.32 x 10.02 x 1.73 吋 (寬 x 深 x 高)
    1U,含機架裝載套件
    大約重量:3.6 公斤

硬體

  • 64MB 的 CPU SDRAM
    16MB 的快閃記憶體
    6Mb 的封包緩衝記憶體

MIB 支援

  • RFC 1213 MIB II
    RFC 1215 標準擷取訊號
    RFC 1286 橋接 MIB
    RFC 1442 SMIv2 (SNMPv2 MIB)
    RFC 1451 管理員對管理員 MIB
    RFC 1492 TACACS+
    RFC 1493 橋接管理物件定義
    RFC 1573 介面革新
    RFC 1643 類乙太 MIB
    RFC 1757 遠端網路監控 (RMON) MIB
    RFC 1907 SNMP v2 MIB
    使用 SMIv2 的 RFC 2011 網際網路通訊協定 (IP) MIB
    使用 SMIv2 的 RFC 2012 傳輸控制通訊協定 (TCP) MIB
    使用 SMIv2 的 RFC 2013 使用者資料電報通訊協定 (UDP) MIB
    使用 SMIv2 的 RFC 2233 介面群組
    RFC 2618 RADIUS MIB
    RFC 2665 類乙太網路介面類型 MIB
    RFC 2666 乙太網路晶片組識別
    供橋接資料流量類別、多重傳播篩選及 VLAN 延伸功能之用的 RFC 2674 MIB (IEEE802.1p/q MIB)
    RFC 2737 ENTITY-MIB
    RFC 2819 RMON MIB
    RFC 2863 介面革新
    Dell 5424 Private MIB

支援的標準

  • IEEE 802.1D
    IEEE 802.1Q
    IEEE 802.1p
    IEEE 802.1w
    IEEE 802.1x
    IEEE 802.2
    IEEE 802.3
    IEEE 802.3I
    IEEE 802.3u
    IEEE 802.3x
    IEEE 802.3z
    IEEE 802.ab
    IEEE 802.3ac
    IEEE 802.3ad
    IEEE 802.1v