城門地堡

出法日期:20071111

可能大家都去過荃灣城門水塘燒過野食，但原來o係5號燒烤場附近，城門水塘東南的孖指徑山，有一個二次世界大戰時遺留下來的軍時建築---城門地堡.。城門地堡座落o係醉酒灣防線，醉酒灣防線o係二次大戰時，英軍為防止日軍進入九龍半島及香港島而於新界南部的大型防禦工事。

最近有位自願人仕leung411255@yahoo.com.hk，佢o係城門地堡所有出入口，分叉路口，重要checkpoint都貼上了有用資料--地圖，方向指示，歷史事件等。佢又清除阻塞地道o既淤泥。真係好感激佢所作的努力。

最好不要一人前往and 帶定電筒。好don't say too much，出發吧!

1. 由城門水塘5號燒烤場出發，沿住麥理浩徑第6段行。行大約10分鐘，見到第一個警告路牌"地道危險 切勿內進"，這就是入口。這是地堡手描地圖。

2. 入口牆壁上會見到由自願人仕 提供的城門地堡地圖和有關資料。

3. 沿住樓梯而下，上面有光的地方，係地堡給日軍佔領之後，給英軍位於昂船洲大炮炸毀。

4. 地道的名稱全是英國的地名，來到個分叉位: 左面去Regent Street，右面去Shaftesbury Avenue

5. 向Shaftesbury Avenue行，會見到"若林隊占領"五個日本漢字。當中"若林"即係日軍中尉"若林東一"，就係佢率領數十名精銳步兵，快速攻陷城門地堡。

6. 據聞若林東一現在供奉係日本戰國神社。

7. 走出Shaftesbury Avenue，上到麥理浩徑。

8. 本應可續走Charing Cross，不過因為淤泥阻塞地道，所以只好沿麥理浩徑上到城門地堡指揮中心OP。

9. OP內相當之大，天花和牆壁，佈滿機關鎗彈同手榴彈做成痕跡。


10. 沿這條路再落去Strand Palace Hotel。

11. 沿路有一個通訊室、一個軍官休息室和兩個廁所。



12. 再落1至2分鐘完全漆黑的樓梯。

13. Strand Palace Hotel有兩個廚房，每有廚房有軍廚灶、食水缸和廚台。



14. 來到一條給淤泥阻塞的地道，相信不久會給leung411255@yahoo.com.hk開通。


15. 沿路折返Shaftesbury Avenue，再去Oxford Street。這是Oxford Street途經其中一個出口。

16. 炮位401，可遠望到沙田。

17. 返回城門水塘。

後感:
- 真係好多謝leung411255@yahoo.com.hk 的努力，希望佢早日成功打通所有地道。
- 慨嘆香港政府的無能，只管去英化，任由有重要歷史教育意義的建築荒廢。This is Hong Kong history, this is our history.

Ref:
城門碉堡 - Ching Dynasty - 晴 - Yahoo! BLOG
醉酒灣防線(維基百科)
Hong Kong Hiking Web: 城門地堡

HTTP Tunneling (Part 1) - Break though your company firewall and proxy

It's very common that a company uses firewall + proxy server to restrict people's internet accessing. For example, you can't go to Jockey Club to buy Mark Six , or you can't download files which file size larger than 10M, and more....

To break all these restrictions, we can use a technique called "HTTP Tunneling" as follow:

1. Setup a SSH server at remote site, e.g. home

2. Set the listening port to 443 (443 is selected because it is the port for SSL which you use for secure web site such e-banking and so HTTP tunneling traffic looks like ordinary SSL connection. If you can use e-banking, then you can use port 443. Port 80 is also OK if 443 is not available)

3. Download and install a SSH client at office - Putty

4. Click Start menu -> All Programs -> Putty -> Putty

5. Click "Session" on the left tree. Enter your home SSH server's IP or hostname and the 443 as port no.

6. Click "Connection" -> "Proxy". Select "HTTP" as proxy type. Enter you office's proxy server's hostname and port. And enter the proxy username and password (This step is required only if you have a proxy server)

7. Click "Connection" -> "SSH" -> "Tunnels". Enter 8080 as "Source Port" and select "Dynamic" and "Auto". Click "Add" button.

8. Click "Session" and enter the anything for "Saved Sessions" name, e.g. SOCKS5. Click "Save" button.

9. Click "Open" button.

10. Enter the SSH server's login name and password.
11. Setup your browser to use SOCKS5:
a) Firefox:
- Click Tools -> Options -> Advanced -> Network -> Settings.
- Enter "localhost" as "SOCKS host" and 8080 as "Port"

b) Internet Explorer:
- Click Tools -> Network Options -> Connections -> LAN Settings -> Advanced
- Enter "localhost" as "Socks" and 8080 as port

Ref:
How to install OpenSSH sshd server and sftp server on a Windows 2000 or Windows XP
Jamyy's Weblog: PuTTY - SSH Tunnel 運用備忘

寧食開眉粥，莫食愁眉飯
雖然口嚐美食，但心郤一直在痛．．．

20070707:
今日我們大約4 點半才到DisneyLand，玩了一會Fantancy Land. 食完晚飯, 坐在城堡前等看9點煙花表演.
放煙花前發生了一件小插曲， 在放煙花前突然有個女子企起身來拍照，大家好齊心的用普通話叫著"坐下，坐下...". 但那女子好像聽不懂似的，照樣企著來拍照， 最後有名男子走到女子身後，拍一拍她肩膀示意坐下. 她才坐下，大家很開心的歡呼了一會，煙花就開始了.

對於大家這樣齊心(就好像"應援團"，全人類齊心救地球一幕)，咁守秩序，真的很高興.
這晚玩得很開心，最後我們到了荃灣路德圍，去到一間叫"小樽甜品屋" (classified as 可以再去)，食了雜果目黑，芒果目黑and薑餅人形狀的朱古力仔，來為這天劃上完美的句號.

20070624:
這日天氣好到不得了，久別了的藍天又再重現
那天我們坐船遊大澳，看到中華白海豚，粉紅色的一團跳出海面，興奮又開心
希望香港多注重環保，保護大自然，不要只在海洋公園才可看到"她們"



P.S. 剛出生的中華白海豚是灰色，而年青的中華白海豚呈淺粉紅色，最後成年的中華白海豚是粉紅色

我地買o左DisneyLand Annual Pass, 可以無限次入disney (除o左X'max and 新年). 如果你地去disney, 記得約埋我地去喎.

P.S. 海盜米奇已經被我地生擒o左喇! 仲有佢D 海盜兄弟...

Happy Birthday

6月9日是Rebecca生日, 原本想去DisneyLand慶祝生日, 因為天雨關係, 改去了杜莎夫人蠟像館, 有好多名星名人陪我地過生日: 古巨基, 碧咸, 陳慧琳...
晚上, 到了山頂餐廳 (The Peak Lookout), 吃了一頓豐富的candle dinner. 環境, 服務 and食物水準我都非常滿意...羊架真的很美味呀!

Rebecca, Happy Birthday!!

We + Sakura + Japan

This Easter, Rebecca and I went to Japan (大阪, 京都 and 東京) for 7 days.
It's very lucky that we can see sakura over there (since it is just open for 1-2 weeks annually).

I must re-visit Japan (in means of 自由行) in the future! ^_^

You can find more photos at:
http://picasaweb.google.com/aoknahc/2007JapanPart1
http://picasaweb.google.com/aoknahc/2007JapanPart2


Steven Chan

Just look at what I took on my mobile, I find this interesting picture...... one man and (i think) his son playing badminton on a tennis court.... one word "勁"

Testing your anti-virus software

I just know that there is a "virus" which is not virus. It is a fake virus for testing purpose.
Detail:
http://www.eicar.org/anti_virus_test_file.htm
http://us.mcafee.com/virusInfo/default.asp?id=description&virus_k=98616

ORA-16136: Managed Standby Recovery not active

Problem:
There is some problem in Oracle Dataguard. I want to switch the standby database to readonly mode. Firstly I cancel the standby managed recovery but it gave me this error:
SQL> alter database recover managed standby database cancel;
ORA-16136: Managed Standby Recovery not active

Solution:
1. Shutdown the standby db
SQL> shutdown immediate;

2. Start the standby
% set ORACLE_SID={ORACLE_SID}
% sqlplus /nolog
SQL> conn / as sysdba
SQL> startup mount;
SQL> alter database recover managed standby database disconnect from session;

2. Inspect the alert log i.e. %ORACLE_HOME%\admin\{ORACLE_SID}\bdump\alert_{ORACLE_SID}.log
===========================================================================
Managed Standby Recovery not using Real Time Apply
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001
Errors with log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001
MRP0: Background Media Recovery terminated with error 328
Fri Feb 02 12:15:48 2007
Errors in file c:\oracle\product\10.2.0\admin\{ORACLE_SID}\bdump\{ORACLE_SID}_mrp0_3800.trc:
ORA-00328: Message 328 not found; No message file for product=RDBMS, facility=ORA; arguments: [48917243] [51266725]
ORA-00334: Message 334 not found; No message file for product=RDBMS, facility=ORA; arguments: [E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001]
===========================================================================

3. Inspect c:\oracle\product\10.2.0\admin\{ORACLE_SID}\bdump\{ORACLE_SID}_mrp0_3800.trc, it shows that MRP0 process tried to start but failed.
===========================================================================
MRP0: Background Managed Standby Recovery process started
*** 2007-02-02 12:15:48.796 1011 krsm.c
Managed Recovery: Initialization posted.
*** 2007-02-02 12:15:48.796 60680 kcrr.c
Managed Standby Recovery not using Real Time Apply
Recovery target incarnation = 2, activation ID = 1875773575
Influx buffer limit = 38173 (50% x 76347)
Start recovery at thread 1 ckpt scn 51266725 logseq 6280 block 2
*** 2007-02-02 12:15:48.906
Media Recovery add redo thread 1
*** 2007-02-02 12:15:48.906 1011 krsm.c
Managed Recovery: Active posted.
*** 2007-02-02 12:15:48.968
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001
*** 2007-02-02 12:15:48.984 60680 kcrr.c
MRP0: Background Media Recovery terminated with error 328
ORA-00328: Message 328 not found; No message file for product=RDBMS, facility=ORA; arguments: [48917243] [51266725]
ORA-00334: Message 334 not found; No message file for product=RDBMS, facility=ORA; arguments: [E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001]
===========================================================================

4. Check the file E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001 (on standby) with the one in primary database. They are different in size!!

5. Copy the ARC06280_0575569794.001 from primary to standby.

6. Shutdown and restart the standby db again.

7. Inspect the alert log on standby again. It seems standby database running normally again!
===========================================================================
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06280_0575569794.001
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06281_0575569794.001
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06282_0575569794.001
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06283_0575569794.001
Media Recovery Log E:\XXX_DB\ARCH\{ORACLE_SID}\ARC06284_0575569794.001
===========================================================================

8. Check the progress of apply of archive.
SQL> select sequence#, to_char(first_time,'YYYY-MM-DD HH24:MI') as first_time,
to_char(next_time,'YYYY-MM-DD HH24:MI') as next_time, applied from v$archived_log order by sequence#;

9. Finally turn off recover of standby and open the db in readonly mode. Great, It runs without error!
SQL> alter database recover managed standby database cancel;
SQL> alter database open read only;

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Don't know why the oracle standby db can't be reached by primary database suddenly (which is working perfectly before). After googling the problem, i found the solution by adding the following into listener.ora:

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = visdev2)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
)
)