我是学软件的现在正在做卡拉ok点歌系统,不知道这个软件数据库最多可以做出几个表啊 请列出来最好10个!

我是学软件的现在正在做卡拉ok点歌系统,不知道这个软件数据库最多可以做出几个表啊 请列出来最好10个!,第1张

歌星库 只分类 歌星类别(如 港台男 港台女 大陆男 大陆女 )

字数塞选 拼音姓氏筛选

歌曲歌曲分类 1类别分类(流行歌曲 民族歌曲 儿童歌曲等 ) 2语言分类 (国语 粤语 日语等) 等等

歌曲名字筛选(这里应该比较复杂了) 首先要做字数排序筛选 拼音及模糊拼音筛选 关联歌星 关联类别等等 你琢磨琢磨

用户数据收藏 个人曲库收藏 等等

排行榜 各种点击和热门排行等等

你研究研究 想得越多 功能越齐全 越有竞争力 不然视易\雷石不会让你出头的

英文版 不懂我可以再给你中文版 慢慢来 别急The purpose of this article is to describe how to recover a database from a total failure using RMAN 8i

This article is meant to assist you in performing an incomplete recovery after losing all datafiles, online redo logs, and control files

You need Oracle Services for the database and an initora file Additionally, if you have archive logs that have not been cataloged, you will be able to use them as part of the recovery

1RESTORE CONTROLFILE

set ORACLE_SID=PROD

svrmgr> connect internal

svrmgr> startup nomount pfile=<initora>

svrmgr> Exit

set ORACLE_SID=PROD

RMAN TARGET INTERNAL/password CATALOG rman/rman@rcat

RMAN> run {

allocate channel c1 type disk;

restore controlfile;

alter database mount;

release channel c1;

}

2QUERY TARGET AND CATALOG DATABASE

Connect to the catalog database and issue the following:

set ORACLE_SID=RCAT

svrmgr> connect rman/rman

svrmgr>

select sequence#, thread#, low_scn, next_scn from rlh;

SEQUENCE# THREAD# LOW_SCN NEXT_SCN

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

188 1 37278

189 1 37891

190 1 38231

191 1 38319

192 1 38389

193 1 38468

194 1 38562

195 1 38649

196 1 38708

197 1 38844

Note the last SCN is 197 This is the last System Change Number that the RMAN catalog is aware of

Now connect to the target database:

set ORACLE_SID=PROD

svrmgr> connect internal

svrmgr> select from v$log_history

RECID STAMP THREAD# SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#

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

188 410011317 1 188 & 37278

189 410011323 1 189 & 37891

190 410011328 1 190 & 38231

191 410011332 1 191 & 38319

192 410011338 1 192 & 38389

193 410011341 1 193 & 38468

194 410011345 1 194 & 38562

195 410011349 1 195 & 38649

196 410011352 1 196 & 38708

197 410011551 1 197 & 38844

Since the database has been mounted using a backup control file, the last Log Sequence Number that the control file is aware of is 197 This happens to match the last LSN known by the catalog because a resync has not been performed since the last backup But if you look in the archive dump destination, you may see additional archive logs that have not been cataloged You need to catalog these files so that RMAN can use them during the recovery

Directory of D:\ORACLE\oradata\PROD\archive

0/03/00 11:46a <DIR>

0/03/00 11:46a <DIR>

0/03/00 12:09p 11,264 PRODT001S00198ARC

0/03/00 12:09p 11,264 PRODT001S00199ARC

0/03/00 12:09p 1,024 PRODT001S00200ARC

0/03/00 12:09p 1,024 PRODT001S00201ARC

3 MANUALLY CATALOG ANY INTERMEDIATE ARCHIVED LOGS

Archive logs 198 through 201 are available but have not been recorded in the catalog

Perform the following for each available archive log:

set ORACLE_SID=PROD

RMAN TARGET INTERNAL/password CATALOG rman/rman@rcat

RMAN> catalog archivelog 'd:\oracle\oradata\prod\archive\PRODT001S00198ARC';

4 RESTORE AND RECOVER DATABASE

The last archive log available has a log sequence number of 201, so you can perform an incomplete recovery using logs up to and including PRODT001S00201ARC

RMAN> run {

allocate channel c1 type disk;

set until logseq 201 thread 1;

restore database;

recover database;

release channel c1;

sql "alter database open resetlogs";

}

5 RESET THE DATABASE

Before you can use RMAN again with a target database that has been opened with the RESETLOGS option, you must notify RMAN that you have reset the database incarnation The reset database command directs RMAN to create a new database incarnation record in the recovery catalog

RMAN> reset database;

RMAN> List Incarnation of database;

List of Database Incarnations

DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time

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

1 2 PROD 4116816026 NO 1 03-OCT-00

1 429 PROD 4116816026 YES 38872 03-OCT-00

6 BACKUP DATABASE

Immediately backup the database Because the database is a new incarnation, the pre-RESETLOG backups are not usable Prior to running the backup, remove the old archive log file from the archive dump destination

RMAN> run {

shutdown immediate;

startup mount pfile=<initora>;

allocate channel c1 type disk format 'e:\oracle\oradata\backup\df_%d_%p_%c_%s';

backup database;

release channel c1;

allocate channel c1 type disk format 'e:\oracle\oradata\backup\archive\al_%d_%s_%c';

backup (archivelog all delete input);

sql 'alter database open';

release channel c1;

}

有两个方法的,1用优盘,接入系统,由点歌系统读取。2到数据库添加,首先把歌曲复制到硬盘的存歌盘,将歌曲名改为纯英文与数字组合,复制歌曲名,到数据库添加,该歌曲,在连接处输入与其他已有歌曲的链接点。进入系统就可以点歌了。第二种比较复杂,但很慢

以上就是关于我是学软件的现在正在做卡拉ok点歌系统,不知道这个软件数据库最多可以做出几个表啊 请列出来最好10个!全部的内容,包括:我是学软件的现在正在做卡拉ok点歌系统,不知道这个软件数据库最多可以做出几个表啊 请列出来最好10个!、急!礼光博软点歌系统数据库、雷石KTV点歌系统,如何从U盘添加歌曲等相关内容解答,如果想了解更多相关内容,可以关注我们,你们的支持是我们更新的动力!

欢迎分享,转载请注明来源:内存溢出

原文地址: http://outofmemory.cn/sjk/9350557.html

(0)
打赏 微信扫一扫 微信扫一扫 支付宝扫一扫 支付宝扫一扫
上一篇 2023-04-27
下一篇 2023-04-27

发表评论

登录后才能评论

评论列表(0条)

保存